Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I've heard some packages being classified as a meta-package. So now I am left wondering what is the difference between a meta-package and a package?

share|improve this question
    
If I may submit a very similar question was asked on another channel… …by me. –  kojiro Oct 14 '11 at 19:26
    
oh... i was just looking into askubuntu.com to see if the question had been asked before. –  nitstorm Oct 14 '11 at 23:56

4 Answers 4

up vote 14 down vote accepted

These packages do not contain actual software, they simply depend on other packages to be installed.

It is important to note that removing a meta package does NOT remove the packages it installed:

when a metapackage is automatically removed by the removal or purging of any one, or more, of its underlying dependencies, all of the other packages that were in the metapackage's depends list are still installed on the system.

You can look at the structure of a typical meta package by pulling (for example) ubuntu-desktop:

apt-get source ubuntu-desktop

and then looking at the structure, you'll find the list of packages each meta-package recommends, as well as the structure of putting it all together in debian/rules.

References:

share|improve this answer
1  
What about update? If i update a metapackage, would the dependencies would also update? –  Kit Ho Apr 17 '13 at 5:46

Metapackages are a link to existing package or packages. So they are essentially a script that installs other packages.They keep the packages as dependencies

Eg: the package ubuntu-desktop installs all the packages needed for the Default UI for ubuntu. But uninstalling the same doesen't uninstall its dependencies

share|improve this answer
    
Thanks for the great answer @AmithKK –  nitstorm Oct 14 '11 at 16:27
    
what about upgrade? upgrade a metapackage would update the dependencies? –  Kit Ho Apr 17 '13 at 5:51

A meta-package pulls in other packages, and by definition should not do anything else.

A package usually has some sort of content (files, applications, documentation, a script, or such).

share|improve this answer
    
Thanks for explaining it in the IM as well :) –  nitstorm Oct 14 '11 at 16:28

Simply said, a meta package has nothing in it, except empty docs. The only thing it has is metadata, which means that it can have dependencies, or conflicts etc...

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.