Hi.
(A special hello to Junichi who is CCed because of his libpkg-guide.)
I'm having a package that will probably use the age feature of release
numbering. (I.e. libfoo.a.b.1 to indicate that programs linked against libfoo.a
and libfoo.(a-1) can use it as documented in the libtool docs.) I've
Hi.
Junichi Uekawa wrote:
You are going to use the SONAME of the library, which will be different
from the numbers you give to the libtool versioning.
The package name is going to be derived from the package name, so
you don't need to play with the provides and such things.
Ah. Thanks.
Now
Hi.
(A special hello to Junichi who is CCed because of his libpkg-guide.)
I'm having a package that will probably use the age feature of release
numbering. (I.e. libfoo.a.b.1 to indicate that programs linked against libfoo.a
and libfoo.(a-1) can use it as documented in the libtool docs.) I've
Hi.
(A special hello to Junichi who is CCed because of his libpkg-guide.)
I'm having a package that will probably use the age feature of release
numbering. (I.e. libfoo.a.b.1 to indicate that programs linked against
libfoo.a
and libfoo.(a-1) can use it as documented in the libtool docs.)
Hi.
Junichi Uekawa wrote:
You are going to use the SONAME of the library, which will be different
from the numbers you give to the libtool versioning.
The package name is going to be derived from the package name, so
you don't need to play with the provides and such things.
Ah. Thanks.
Now
5 matches
Mail list logo
