Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On our local repository, we'd like to create a "product" install that includes all of our packages. The two ways that seem possible to do this is do create a "blank" package called 'product' that depends on all our other rpms. Or we can create a group package in yum that includes all of those rpms.

A quick google, I couldn't find a pro/con of either approach. Anyone have an opinion on either direction?

share|improve this question
up vote 2 down vote accepted

Creating a metapackage means that all the packages it depends on must be installed, with no chance for customization of capabilities due to presence or absence of the various packages. This can be fixed by removing the metapackage before removing other packages, but users aren't always certain whether or not the metapackage can be removed safely.

A yum group allows all the packages to be installed at once, but also allows pick-and-choose without frustrating the end user. This can cause issues if a user installs only specific packages manually without installing enough for the application to be functional, but accurate interdependencies between the various application packages should make sure that a minimum set is installed when any of them are chosen.

share|improve this answer

metapackage needs to use yum to install all the dependencies, if yum can't find one of the dependencies, metapackage can't be installed successfully. a "product" install that includes all of our package, can be install by rpm command, we don't need to resolve dependencies for it.

share|improve this answer

Your Answer


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.