Re: Shared library dependencies revisited

1996-08-14 Thread Ian Jackson
Bruce Perens writes ("Re: Shared library dependencies revisited"): ... > OK. Have each library-provider automaticaly include a "Provides: " for > each library that it provides, with the name indicating the > architecture, executable format, soname, and major and _mi

Re: Shared library dependencies revisited

1996-08-14 Thread Bruce Perens
Bruce: > We can make your proposal simpler by using virtual package names to > find the libraries.[ eg Provides: libX11.so.6 ] From: Ian Jackson <[EMAIL PROTECTED]> > As it stands there are a couple of problems: > [...] we need to depend on a particular version of the package > [...] some pack

Re: Shared library dependencies revisited

1996-08-13 Thread Ian Jackson
Bruce Perens writes ("Re: Shared library dependencies revisited"): ... > We can make your proposal simpler by using virtual package names to > find the libraries.[ eg Provides: libX11.so.6 ] This is a very interesting idea, thanks for the suggestion. As it stands there

Re: Shared library dependencies revisited

1996-08-13 Thread Ian Jackson
Mark Eichin writes ("Re: Shared library dependencies revisited"): > >> libc.so.5 libc5 (>= 5.2.18-2) > > Hmm. How are we going to determine the minor versions? I run an > "unstable" system and use it for my development -- but my packages are >

Re: Shared library dependencies revisited

1996-08-13 Thread Ian Jackson
Maarten Boekhold writes ("Re: Shared library dependencies revisited"): ... > And what about packages that depend on *one* particular version of a > library? I know of one library which will cause trouble, namely libslang. > This library changes every minor version update so tha

Re: Shared library dependencies revisited

1996-08-12 Thread Bruce Perens
Ian, We can make your proposal simpler by using virtual package names to find the libraries. Each package that provides a shared library should, for each shared library that it provides, automaticaly add something like "Provides: libX11.so.6" to the control file. Each package that depends on a li

Re: Shared library dependencies revisited

1996-08-12 Thread Maarten Boekhold
> I propose the following arrangement (if you don't understand things > you should read dpkg-source(1) and the relevant parts of the new > programmers' manual): > > Every package which contains compiled binaries invokes, in its > debian/rules, a program which automatically determines what the > de

Shared library dependencies revisited

1996-08-12 Thread Ian Jackson
Please read the proposal below and comment on it. If noone says anything I'll probably implement and mandate something very like it in the next week or two, in time for the new source package format (we only want to change this once). Now is the time to have your say. I've been thinking about sh