Server Fault is a question and answer site for system and network administrators. 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

I would like all of my organizations RPMs to have a vendor defined so we can easily see which of our RPMs are installed. Does anyone know why Fedora says:

Do not use these tags:

They give no reasoning at all.

If not using "Vendor" are there recommendations as to another method that is commonly used for this purpose?

share|improve this question

This has to do with RPMs generally. Has good details, but....

  • Packager Best used if your RPMs are never, ever going to be repackaged by anyone.
  • Vendor Frequently auto-set by build systems (so it may be good in your case).
  • Copyright Deprecated in favor of the License tag.
share|improve this answer
The Fedora Packaging Guidelines state: The Vendor tag should not be used. It is set automatically by the build system. – Michael Hampton Oct 18 '12 at 16:33
Thanks Michael, but currently I don't see any vendor being set. For example, if I do rpm -qi <mypackage> | grep -i vendor nothing is printed. Where as for most other packages on my system the vendor is "Fedora Project". – user800133 Oct 18 '12 at 16:55

The Packager tag discouragement is poorly worded--I think the intent would be clearer something like this: "Don't hard-code your name in the Packager field in the RPM specfile. The rpmbuild tool will fill it in from the macro, if defined." Where macro can be defined like this:

rpmbuild --define "packager $USER@$HOSTNAME" | grep -i packager

-8: packager
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.