Vendor created RPM naming.

["Ace Nimrod" <ace.nimrod@xxxxxxxxx>]

We provide our product as a set of RPMs for RedHat 4/CentOS 4 (and soon 5) and we require some RPMs that are upgrades of the base RPMs.  To prevent conflicts we install all our packages in /opt/<vendorname> and prefix all RPM packages with <vendorname>.  This will prevent us from overwriting any other RPMs, as well as RPMs overwriting ours.

Is this sane?

So for example, we provide our own foobar package which is an upgrade to foobar in CentOS 4, we'd name it like..
  <myvendor>.foobar-1.2.3-1.el4

Is there a better approach to take with this?  So far it seems to work just fine.

Thanks.

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list