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

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

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

2006-05-17 Thread John Bowler
From: Ralf Wildenhues [mailto:[EMAIL PROTECTED] John Bowler: The issue here is that libpng on irix has (currently) a major version number of '0', as it does on all other operating systems. Why should the version number be constant across operating systems? It isn't. The *major* version

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

2006-05-17 Thread John Bowler
From: Ralf Wildenhues [mailto:[EMAIL PROTECTED] John Bowler: The issue here is that libpng on irix has (currently) a major version number of '0', as it does on all other operating systems. Why should the version number be constant across operating systems? It isn't. The *major* version

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

2006-05-16 Thread John Bowler
weird that libtool should make a major version number of 0 impossible and not offer any explanation of what is going on. John Bowler [EMAIL PROTECTED] ___ http://lists.gnu.org/mailman/listinfo/libtool

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

2006-04-01 Thread John Bowler
from the two bugs (failure in 'none' and irix fails if the major version number is 0) we haven't seen any problems (yet). John Bowler [EMAIL PROTECTED] ___ http://lists.gnu.org/mailman/listinfo/libtool