You might want to refer to the libtool-doc package: 'info libtool' and go
to the Menu node on Versioning. That is the source of the message you
quoted and it contains more information as well.
On Mon, Apr 30, 2001 at 10:35:12AM -0400, [EMAIL PROTECTED] wrote:
> > Yes, but now I have another ques
You might want to refer to the libtool-doc package: 'info libtool' and go
to the Menu node on Versioning. That is the source of the message you
quoted and it contains more information as well.
On Mon, Apr 30, 2001 at 10:35:12AM -0400, [EMAIL PROTECTED] wrote:
> > Yes, but now I have another que
On 30 Apr 2001, Jose Carlos Garcia Sogo wrote:
> El 30 Apr 2001 09:37:23 -0400, [EMAIL PROTECTED] escribió:
> [...]
> > Nothing happens to the old package.
> > When a new shared library comes out that is incompatible with an old
> > shared library, both libraries should be installed, this is why
> Yes, but now I have another question. The library itself has a
> different version numbering.
That's ok. Version number and SO name are not the same and need not
have any correlation. Many different versions can have the same soname
and that's ok.
> In this way, current version is 0.2.1, but
On Mon, Apr 30, 2001 at 01:22:03PM +0200, Jose Carlos Garcia Sogo wrote:
> OK, let's say now that the current is increased, and the new name of the
> library is libgpgme.so.1.0.0. This means that I should change in the
> debian/control file the name of the package and it will become libgpgme1
> but
Jose Carlos Garcia Sogo <[EMAIL PROTECTED]> writes:
JCGS> I'm trying to package a library, but I have some questions regarding
JCGS> the name the package should have.
JCGS>
JCGS> First of all, the policy says that the library package must something
JCGS> like libpackagesoname, so if the library
El 30 Apr 2001 09:37:23 -0400, [EMAIL PROTECTED] escribió:
[...]
> Nothing happens to the old package.
>
> When a new shared library comes out that is incompatible with an old
> shared library, both libraries should be installed, this is why the
> soname is in the package name. It allows simult
> OK, let's say now that the current is increased, and the new name of the
> library is libgpgme.so.1.0.0. This means that I should change in the
> debian/control file the name of the package and it will become libgpgme1
> but, what happens with the old package (libgpgme0) and with the programs
> c
Hello!
I'm trying to package a library, but I have some questions regarding
the name the package should have.
First of all, the policy says that the library package must something
like libpackagesoname, so if the library that the package has looks
like:
lrwxrwxrwx1 jose jose
On 30 Apr 2001, Jose Carlos Garcia Sogo wrote:
> El 30 Apr 2001 09:37:23 -0400, [EMAIL PROTECTED] escribió:
> [...]
> > Nothing happens to the old package.
> > When a new shared library comes out that is incompatible with an old
> > shared library, both libraries should be installed, this is why
> Yes, but now I have another question. The library itself has a
> different version numbering.
That's ok. Version number and SO name are not the same and need not
have any correlation. Many different versions can have the same soname
and that's ok.
> In this way, current version is 0.2.1, bu
On Mon, Apr 30, 2001 at 01:22:03PM +0200, Jose Carlos Garcia Sogo wrote:
> OK, let's say now that the current is increased, and the new name of the
> library is libgpgme.so.1.0.0. This means that I should change in the
> debian/control file the name of the package and it will become libgpgme1
> bu
Jose Carlos Garcia Sogo <[EMAIL PROTECTED]> writes:
JCGS> I'm trying to package a library, but I have some questions regarding
JCGS> the name the package should have.
JCGS>
JCGS> First of all, the policy says that the library package must something
JCGS> like libpackagesoname, so if the library
El 30 Apr 2001 09:37:23 -0400, [EMAIL PROTECTED] escribió:
[...]
> Nothing happens to the old package.
>
> When a new shared library comes out that is incompatible with an old
> shared library, both libraries should be installed, this is why the
> soname is in the package name. It allows simul
> OK, let's say now that the current is increased, and the new name of the
> library is libgpgme.so.1.0.0. This means that I should change in the
> debian/control file the name of the package and it will become libgpgme1
> but, what happens with the old package (libgpgme0) and with the programs
>
Hello!
I'm trying to package a library, but I have some questions regarding
the name the package should have.
First of all, the policy says that the library package must something
like libpackagesoname, so if the library that the package has looks
like:
lrwxrwxrwx1 jose jose
16 matches
Mail list logo
