RE: [png-mng-implement] -version-number and BeOS

2006-05-19 Thread John Bowler
From: Glenn Randers-Pehrson
>On 5/17/06, John Bowler <[EMAIL PROTECTED]> wrote:
>> 3) We could change the major version to be (say) '1' at the next
major
>>   release, but we can't change it in libpng 1.2.x
>
>Should we do that?  We haven't, so far, in 1.4.0betaN.  We could skip
right to 1.4.1 now.

I think we should do that in 1.4.0betaN+1 - there's no reason to skip
to 1.4.1.  It just means that the shared library will be libpng14.so.1,
rather than libpng14.so.0.  The number '0' (current) or '1' (proposed)
is hardwired in Makefile.am

That looks like a major release, but since 1.4.0 is still in beta the
preceding major - libpng14.so.0 - was never public.

Notice that in 1.4.x 'x' is the *minor* release.  So we have:

libpng 1.2.9 --> libpng12.so.0.9.0
libpng 1.2.10 --> libpng12.so.0.10.0
libpng 1.4.0 --> libpng14.so.0.0.0 (currently)
libpng 1.4.0 --> libpng14.so.1.0.0 (proposed)

The 'compatibility' named library (libpng.so.3) shouldn't be generated
by 1.4 (at least, I think that is what we agreed - there is absolutely
no reason to generate it!)

John Bowler <[EMAIL PROTECTED]>





Re: [png-mng-implement] -version-number and BeOS

2006-05-19 Thread Glenn Randers-Pehrson

On 5/17/06, John Bowler <[EMAIL PROTECTED]> wrote:


3) We could change the major version to be (say) '1' at the next major
  release, but we can't change it in libpng 1.2.x


Should we do that?  We haven't, so far, in 1.4.0betaN.  We could skip
right to 1.4.1 now.

Glenn