There are several examples of packaging where an application package is built, named, described, even licensed, but contains only setup code and dependencies -- it has no first-class runtime software of its own. I would call this "meta-packaging".

This seems to be particularly popular in the open-source world, including examples like kde-meta (Gentoo Portage), Plone, and I'm sure lots of others. I can see how it's a useful practice, but despite it existing as a practice, I couldn't find a formal definition of either "meta-packaging" or "meta-egg" (Python) in searching the web. Is that not the correct term? If it is, is it such common-sense that it needs no formal definition? If not, what is the correct way to put it?

1 Answer 1


I would describe a meta-package just has you described it: A collection of software and dependencies distributed as a single package with no or extremely little code of its own.

You could use Debian or RPM packages as an example: You have meta packages that install nothing but dependencies and programs that most people want.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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