Re: libgtk1.1
On Tue, 10 Nov, 1998, Ben Gertzfield wrote:
> Michael> We can. We can package it as libgtk1.12 resp. libgtk1.13
> Michael> etc. so the old version can coexist. That way we can
> Michael> follow the development without breaking the other
> Michael> packages.
>
> Well, that's a kludge that will take up huge amounts of space on
> mirrors. I guess I can do it, but I'll wait for the next gtk+ 1.1
> release.
That ain't no kludge. I suggest you read the policy document again.
4.3. Shared libraries
---------------------
...
For a straightforward library which has a development environment and
a runtime kit including just shared libraries you need to create two
packages: `<libraryname><soname>' (<soname> is the shared object name
of the shared library--it's the thing that has to match exactly
between building an executable and running it for the dynamic linker
to be able run the program; usually the <soname> is the major number
of the library) and `<libraryname><soname>-dev'.
...
Packages which use the shared library should have a dependency on the
name of the shared library package, `<libraryname><soname>'. When the
<soname> changes you can have both versions of the library installed
while moving from the old library to the new.
--
GNU does not eliminate all the world's problems, only some of them.
-- The GNU Manifesto
Reply to: