Once again: libc6 packages compatibility etc...

[Philippe Troin <phil@fifi.org>]

I know this has been debated at length, but the few libc6 libraries 
we have are not extremely explicit on this.
Assuming I want to package libfoo5 for libc6, I should create:

	libfoo5g: 
		o Contains shared libs in /usr/lib compiled with libc6
	libfoo5g-dev:
		o Contains includes in /usr/include
		o Contains static libs in /usr/lib + the .so symlink
		  pointing to /usr/lib
	libfoo5:
		o Contains shared libs in /usr/lib/libc5-compat,
		  compiled for libc5
	libfoo5-altdev:
		o Contains includes in /usr/i486-linuxlibc1/include
		o Contains static libs in /usr/i486-linuxlibc1/lib + the
		  .so symlink pointing to /usr/lib/libc5-compat.

Is that correct (including the `g' placement) ?

Is it acceptable that libfoo5 depends on libfoo5g ? I think so 
because:
  1) When upgrading, dselect will automagically grab the libc6 library
  2) Some documentation for example can be put in libfoo5g only.

Is it acceptable that libfoo5-altdev depends on libfoo5g-dev ?
My reasons are:
  1) The library manpages can be put in the libfoo5g-dev package.

And finally, for seldomly used libraries (I'm thinking mainly of a 
library package which is only used with one package, eg 
libmagick/imagemagick), is it acceptable to have only libc6 libraries 
(aka no `g', no altdev, only libmagick compiled libc6) ?

Phil.



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .