Subject: Re: so name bump; impact on major, minor and patch version

Re: so name bump; impact on major, minor and patch version

From: Daniel Stenberg <daniel_at_haxx.se>
Date: Sun, 14 Mar 2010 19:57:31 +0100 (CET)

On Sun, 14 Mar 2010, Jose Baars wrote:

>> You should not use the libssh2 release version number for the library
>> version on VMS -- please compute the shared library version from the
>> '-version-info 1:1:0' information in src/Makefile.am. The release version
>> number of libssh2 has nothing to do with shared library versioning,
>> strictly speaking. See the comments in src/Makefile.am for more
>> background, or read the GNU Libtool manual for the entire story.
>>
>>
> I had a discussion with some VMS people about this, and that is not very
> practical or even feasable on VMS due to the different way .so is
> implemented on unixes and VMS.

It is feasable, even if not optimal, on VMS since I know we do exactly like
that in other projects that also build on VMS...

If not using libtool and their suggested way of numbering the libs, what
exactly are you suggesting? And isn't the problem you refer to rather a
problem with libtool rather than with libssh2?

-- 
  / daniel.haxx.se
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2010-03-14