Minor nitpick maybe, but normally the release part of an RPM name is used only for RPM specific changes, e.g. if the RPM maintainer made changes to the packaging or patches applied. (name-ver-rel-arch.rpm) So, shorewall-1.3-0.noarch.rpm would normally be shorewall-1.3.0-0.noarch.rpm ..and the second attempt of getting the RPM packaging right would be shorewall-1.3.0-1.noarch.rpm ..next shorewall version would be shorewall-1.3.1-0.noarch.rpm /magnus
On Mon, 10 Jun 2002, Magnus Stenman wrote:> Minor nitpick maybe, but normally the release part of an > RPM name is used only for RPM specific changes, e.g. if > the RPM maintainer made changes to the packaging or patches applied. > > (name-ver-rel-arch.rpm) > > > So, shorewall-1.3-0.noarch.rpm > > would normally be > > shorewall-1.3.0-0.noarch.rpm > ..and the second attempt of getting the RPM packaging right would be > shorewall-1.3.0-1.noarch.rpm > ..next shorewall version would be > shorewall-1.3.1-0.noarch.rpm > >Thanks, -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net
Magnus Stenman schrieb:> > Minor nitpick maybe, but normally the release part of an > RPM name is used only for RPM specific changes, e.g. if > the RPM maintainer made changes to the packaging or patches applied.I''d like to see this change too. I have built slightly modified shorewall RPMs in the past and missed the RPM release part of the name too. Simon> > (name-ver-rel-arch.rpm) > > So, shorewall-1.3-0.noarch.rpm > > would normally be > > shorewall-1.3.0-0.noarch.rpm > ..and the second attempt of getting the RPM packaging right would be > shorewall-1.3.0-1.noarch.rpm > ..next shorewall version would be > shorewall-1.3.1-0.noarch.rpm > > /magnus > _______________________________________________ > Shorewall-devel mailing list > Shorewall-devel@shorewall.net > http://www.shorewall.net/mailman/listinfo/shorewall-devel