Re: Control fields for libraries and programs depending on them

On Tue, Jul 29, 2003 at 08:06:38PM -0400, Neil Roeth wrote: > Suppose there is a package foobar that depends on a library libfoo. AIUI, > whenever the SONAME changes, the library name should change, so I expect > this to evolve as libfoo1, libfoo2, etc. What are the proper control > fields (Depe

Control fields for libraries and programs depending on them

Suppose there is a package foobar that depends on a library libfoo. AIUI, whenever the SONAME changes, the library name should change, so I expect this to evolve as libfoo1, libfoo2, etc. What are the proper control fields (Depends, Conflicts, Replaces, Provides) for these packages? If I underst

Re: Control fields for libraries and programs depending on them

On Tue, Jul 29, 2003 at 08:06:38PM -0400, Neil Roeth wrote: > Suppose there is a package foobar that depends on a library libfoo. AIUI, > whenever the SONAME changes, the library name should change, so I expect > this to evolve as libfoo1, libfoo2, etc. What are the proper control > fields (Depe

Control fields for libraries and programs depending on them

Suppose there is a package foobar that depends on a library libfoo. AIUI, whenever the SONAME changes, the library name should change, so I expect this to evolve as libfoo1, libfoo2, etc. What are the proper control fields (Depends, Conflicts, Replaces, Provides) for these packages? If I underst