[Andreas Metzler]
> [EMAIL PROTECTED] wrote:
> > Is there a way to force a specific library version known in
> > ${shlibs:Depends} ?
>
> Why would you want to do that?
Don't know about the original poster, but here's my reason: I want to
reduce user confusion. Most of the interesting bits of su
Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>> Usually because the binaries shipped with the package use internal,
>> undocumented interfaces that are not available to the rest of the world
>> and hence are not considered part of the SONAME (i.e., up
Russ Allbery <[EMAIL PROTECTED]> writes:
> Andreas Metzler <[EMAIL PROTECTED]> writes:
>> [EMAIL PROTECTED] wrote:
>
>>> Is there a way to force a specific library version known in
>>> ${shlibs:Depends} ?
>
>>> Using "Depends: ${shlibs:Depends}" is not really fine, if I want to
>>> force the libra
On Sunday 16 April 2006 22:13, Steve Langasek wrote:
> Now, the clean solution for those cases when there's a compelling
> reason to implement this bad idea: see what dpkg-shlibdeps(1) has to
> say about shlibs.local.
One minor gripe about dpkg-shlibdeps(1)...
If I look at that page, I get redire
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> On Sun, Apr 16, 2006 at 01:19:36PM -0700, Russ Allbery wrote:
>> I've tried to do this before and encountered:
>>See dpkg-shlibdeps(1) for details of the format of shared library
>>dependency files.
>> which of course is recursive and that man pa
On Sun, Apr 16, 2006 at 01:19:36PM -0700, Russ Allbery wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
> > Now, the clean solution for those cases when there's a compelling reason
> > to implement this bad idea: see what dpkg-shlibdeps(1) has to say about
> > shlibs.local.
>
> I've tried t
Steve Langasek <[EMAIL PROTECTED]> writes:
> Now, the clean solution for those cases when there's a compelling reason
> to implement this bad idea: see what dpkg-shlibdeps(1) has to say about
> shlibs.local.
I've tried to do this before and encountered:
See dpkg-shlibdeps(1) for details of t
On Sun, Apr 16, 2006 at 12:18:58PM +0200, [EMAIL PROTECTED] wrote:
> Hi folks,
> Is there a way to force a specific library version known in
> ${shlibs:Depends} ?
> Using "Depends: ${shlibs:Depends}" is not really fine, if I want to
> force the library to be upgraded when the primary binary packa
Russ Allbery <[EMAIL PROTECTED]> writes:
> Andreas Metzler <[EMAIL PROTECTED]> writes:
>> [EMAIL PROTECTED] wrote:
>>> Is there a way to force a specific library version known in
>>> ${shlibs:Depends} ?
>>> Using "Depends: ${shlibs:Depends}" is not really fine, if I want to
>>> force the library
[EMAIL PROTECTED] writes:
> Hi folks,
>
> Is there a way to force a specific library version known in
> ${shlibs:Depends} ?
>
> Using "Depends: ${shlibs:Depends}" is not really fine, if I want to
> force the library to be upgraded when the primary binary package is
> updated.
>
> However,
> Depend
Andreas Metzler <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
>> Is there a way to force a specific library version known in
>> ${shlibs:Depends} ?
>> Using "Depends: ${shlibs:Depends}" is not really fine, if I want to
>> force the library to be upgraded when the primary binary package i
* Daniel Stone:
> Why? If your library's ABI is changing with every revision, you should
> be bumping the soversion.
Or you shouldn't provide a DSO at all.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
* [EMAIL PROTECTED] [Sun, 16 Apr 2006 12:18:58 +0200]:
> I could abandon the use of ${shlibs:Depends}, and list each dependencies
> manually, but this is a bit annoying.
No, it is not annoying. It is an utterly incorrect thing to do, so
better forget that the idea ever crossed your mind. ;-)
[EMAIL PROTECTED] wrote:
> Is there a way to force a specific library version known in
> ${shlibs:Depends} ?
> Using "Depends: ${shlibs:Depends}" is not really fine, if I want to
> force the library to be upgraded when the primary binary package is
> updated.
Why would you want to do that?
On Sun, Apr 16, 2006 at 12:18:58PM +0200, [EMAIL PROTECTED] wrote:
> Is there a way to force a specific library version known in
> ${shlibs:Depends} ?
>
> Using "Depends: ${shlibs:Depends}" is not really fine, if I want to
> force the library to be upgraded when the primary binary package is
> upd
Hi folks,
Is there a way to force a specific library version known in
${shlibs:Depends} ?
Using "Depends: ${shlibs:Depends}" is not really fine, if I want to
force the library to be upgraded when the primary binary package is
updated.
However,
Depends: ${shlibs:Depends}, libmypackage1 (= ${Sourc
16 matches
Mail list logo
