I just learned from some CMake list traffic that the CMake developers are
struggling with this Mac OS X issue at the moment. It appears they may end
up eventually copying the libtools cross-platform scheme for dealing with
library versioning, see the on-going discussion at
http://public.kitware.com
On 2008-04-03 20:20+0200 Rafael Laboissiere wrote:
> * Alan W. Irwin <[EMAIL PROTECTED]> [2008-04-03 10:51]:
>
>> However, to help the PLplot upstream developers make the decision, please
>> answer my question about how much practical Debian packaging work is
>> required by you to do a major versi
On 2008-04-03 18:51+0200 Rafael Laboissiere wrote:
> * Alan W. Irwin <[EMAIL PROTECTED]> [2008-04-03 08:50]:
>
>> I would prefer not to have different library version numbers for different
>> platforms since that is potentially confusing for everybody and propagates
>> indefinitely.
>
> You could
On behalf of Rafael who is not subscribed to this list.
Alan
__
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implement
On 2008-04-03 10:23+0200 Rafael Laboissiere wrote:
> * Alan W. Irwin <[EMAIL PROTECTED]> [2008-04-02 16:30]:
>
>> Assuming this really is a serious issue on Mac OS X, the obvious solution is
>> to deal with it by bumping the major version number of the above libraries
>> (and libLASi) from 0 to 1.
Although Rafael no longer subscribes to the plplot-devel list, I am
CCing him because he used to be our expert on library version numbers, and
he is still helping Andrew with the Debian packaging of PLplot.
It has just now come to my attention that the major version number for some
of our librarie
