pbxt-discuss team mailing list archive

[Paul McCullagh <paul.mccullagh@xxxxxxxxxxxxx>]

OK, thanks for the tip.

Then I will include the incremental (or bug-fix) release letter in the  
name of the tarball in the future.

I am actually thinking of moving to a different notation for the  
incremental release numbering.

Maybe something like 1.0.10-1, 1.0.10-2, etc.

Then it is easier to see at a glance how many bug fix releases there  
have been.

On Mar 18, 2010, at 7:02 PM, Brian Evans wrote:

> On 3/15/2010 4:46 PM, Paul McCullagh wrote:
> > Hi Brian,
> >
> > Yup, you are right. We should get the tarball out for 1.0.10h.
> >
> > The Windows bug fix was significant.
> >
> > Will do ASAP :)
>
> Once small issue: the tarballs for incremental releases use the same
> file name.
>
> This causes issues for distributors, such as Gentoo, who use hash and
> size manifests to verify the validity of source tarballs.
> The match is made on file name versus several mechanisms (RMD160,  
> SHA1,
> SHA256).
>
> In the case of Gentoo, keeping the file names the same will either:
> 1. Block users from getting updates since the mirrors will reject them
> due to hash/size mismatch.
> 2. Cause errors to users who build after a release.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~pbxt-discuss
> Post to     : pbxt-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~pbxt-discuss
> More help   : https://help.launchpad.net/ListHelp



--
Paul McCullagh
PrimeBase Technologies
www.primebase.org
www.blobstreaming.org
pbxt.blogspot.com