Re: RFC: policy supplement for library packages
...
> based on | package name | library location
> --------------------------------------------
> libc6 | libfoo | /usr/lib/libfoo.so.<ver>
> libc5 | libfoo-libc5 | /usr/lib/libc5-compat/libfoo.so.<ver>
>
...
> based on | package name | hierarchy locations
> ---------------------------------------------------------------
> libc6 | libfoo-dev | /usr/{lib,include}
> libc5 | libfoo-libc5-altdev | /usr/i486-linuxlibc1/{lib,include}
why not put the libs in /usr/i486-includelibc1/lib ?
(or better : why are they in /usr/lib/libc5-compat ?)
> Currently gcc uses none of these schemes.
??? altgcc is installed in /usr/i486-linuxlibc1/bin, and it works fine,
compiling something with prepending this path.
missing : a timeline for all libraries to be compiled.
and one more question:
current libc5 program require libxxx.
the new "libxxx" package will provide these lib, but as libc6 binary.
will the program still work ? (some people will not install the -libc5,
because there is no dependency to use it).
regards, andreas
--
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 .
Reply to: