On Sat, Dec 08, 2007 at 03:22:21PM +0000, Jonathan Underwood wrote:
> Hi Tom,
> 
> I co-maintain the Fedora RPMs for Fedora and I noticed what I think is
> a rather confusing situation in the 4.0.6 release tree.
> 
> In shorewall-4.0.6/ we have, amongst other things:
> 
> shorewall-perl-4.0.6-2.tar.bz2
> shorewall-perl-4.0.6-1.tar.bz2
> shorewall-perl-4.0.6.tar.bz2
> 
> with the -X denoting the patch level. The problem is that rpm (and
> perhaps deb, not sure) doesn't allow a "-" in the upstream version
> number, as that is reserved for the separator between the upstream
> version number and the package release number. This problem actually
> manifest itself in your provided RPMs, eg:
> 
Actually, .deb does not have this limitation.  However, I have decided
to keep to just the x.y.z pattern for the upstream release (in order to
facilitate different Debian revisions of the same upstream version
having the proper dependency).

> shorewall-perl-4.0.6-2.noarch.rpm
> 
> where the patch level has been used for the RPM release number. From a
> distro packaging perspective this doesn't work, because any change to
> the package requires an increase in the package release number (the
> number after the "-"). The only option for packagers is to turn the
> version number into eg. 4.0.6.2. It would be much more helpful if you
> would adopt such a convention upstream though - i.e. indicate the patc
> level with a 4th minor version number rather than a hyphenated number.
> Is that possible?
> 
What I have done with the Debian packages is to just take the patches
for these minor patch releases and put them in the debian/patches/
folder so that they simply get applied at package build time.  That
allows me to keep the upstream version as just x.y.z.  Then I just
increment the -w for the Debian revision.  Of course, that could
potentially cause some confusion, but I have judged that possibility to
be fairly small, as most people who use the Debian packages will use the
Debian packages exclusively.

> Also, I notive that in errata/patches/Shorewall-perl/ there is only
> patch-perl-4.0.6-1.diff and no patch-perl-4.0.6-2.diff. Is this an
> oversight?
> 
I am not sure about this.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com

Attachment: signature.asc
Description: Digital signature

-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel

Reply via email to