On Wed, Jun 13, 2001 at 11:40:28PM +0200, Ove Kaaven wrote:
> I have a library package at version 2.01, and the soversion in it is 0.0.0
> (seems upstream hadn't heard about library versioning). Now, I'm
> considering packaging a new upstream version (2.3.4, still in prerelease
> though), but they
Please read the libtool info files. Library versions != Source versions.
Library versions are dependent on binary-compatibility, or should be,
and this is fully documented in the package 'libtool-doc' in the
section on Versioning. And then forward the information to
upstream so that they know, as
I have a library package at version 2.01, and the soversion in it is 0.0.0
(seems upstream hadn't heard about library versioning). Now, I'm
considering packaging a new upstream version (2.3.4, still in prerelease
though), but they *still* haven't heard about library versioning, so
compiling the new
On Wed, Jun 13, 2001 at 11:40:28PM +0200, Ove Kaaven wrote:
> I have a library package at version 2.01, and the soversion in it is 0.0.0
> (seems upstream hadn't heard about library versioning). Now, I'm
> considering packaging a new upstream version (2.3.4, still in prerelease
> though), but they
Please read the libtool info files. Library versions != Source versions.
Library versions are dependent on binary-compatibility, or should be,
and this is fully documented in the package 'libtool-doc' in the
section on Versioning. And then forward the information to
upstream so that they know, a
I have a library package at version 2.01, and the soversion in it is 0.0.0
(seems upstream hadn't heard about library versioning). Now, I'm
considering packaging a new upstream version (2.3.4, still in prerelease
though), but they *still* haven't heard about library versioning, so
compiling the ne
6 matches
Mail list logo
