I'd like to put forth a point or two of concern in the way that folks are
naming their contrib RPMs.  Informal devinfo convention has developers
putting their initials in the rpm name if they made the rpm and the work
devinfo in the rpm if the project was a group effort.  While this a good
concept and lets a person know who made the RPM, it can cause upgrade
problems down the line.  For example:

Lets say that I write an RPM and name it GJZ.XXX.XXX.rpm.  Later a few
others put in their two cents and the rpm gets renamed to
devinfo.xxx.xxx.rpm.  When users attempt to upgrade the GJZ rpm to the
devinfo rpm, a conflict will very likely occur.  In fact, I had this very
thing happen recently.  When I asked the lead developer what needed to be
done to resolve the conflict, he told me to use the --force option.  :-(

The significant ramification of this is that you could inadvertently folk
your SME box to the point that upgrade can be difficult.  I propose this:

1.  If a project is based on SME standards, leave the name alone and add
your initials to the RPM spec file.  I understand that it's nice to be able
to distiguish a Mitel made rpm from a devinfo made rpm, but this really
muddies the waters.

2.  If a project is based GPL software not written by the devinfo people or
person making the rpm, use the software name in the rpm title with some term
distingising it has been built to run on SME.  For example: 
SME-softwarename.xxx.xxx.rpm.

3.  If a devinfo team or person writes software and builds an rpm from this
software, create a name for the software in question and use the naming
convention outlined in bullet two, above.

4.  Don't put your initials in the RPM version number (e.g.
bind.8.2.2.gjz.i386.rpm, but in the RPM spec file and change the version
number of the RPM using standard practice.

5.  Don't change the base name of and RPM unless there is good reason to do
so.  Again, the RPM spec file provides ample opportunity to list changes and
who made them.  Tracking changes in the RPM name only makes things confusing
down the line.

My two cents. :)  Thank you.
Regards,


--
Greg J. Zartman, P.E.
Vice-President

Logging Engineering International, Inc.
1243 West 7th Avenue
Eugene, Oregon 97402
541-683-8383    fax 541-683-8144


--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org

Reply via email to