Re: possible mass-filing of bugs: many shared library packages contain binaries in usr/bin
Brian May <bam@snoopy.apana.org.au> immo vero scripsit:
> I think we are getting threads crossed here. This thread has nothing to
> do with the other thread I started on libreadline.
Yes... I've had 3 threads to play with. Too bad.
> The initial question is what happens if a package containing a shared
> library contains other binaries?
>
> There seemed to be three solutions:
>
> 1. each version of the shared library conflicts. Not really a
> solution.
> 2. move the binary to a separate package.
> 3. use update alternatives on the binary, so it doesn't need to
> conflict any more.
Sounds good.
Thanks for summing things up.
4. use /libexec or whatever scheme, of naming binaries distinctly according to
shared library soversions. (well, same as 3, I suppose)
the solution in 2. can be used and is documented in policy,
for many of the programs which are just demonstration programs
for the shared library.
regards,
junichi
--
dancer@debian.org : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Libpkg-guide: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: