Helmut Geyer <[EMAIL PROTECTED]> writes:
> based on | package name| hierarchy locations
> ---
> libc6 | libfoo-dev | /usr/{lib,include}
> libc5 | libfoo-libc5-altdev | /usr/i486-linuxlibc1
> libc6 | libfoo-dev | /usr/{lib,include}
> libc5 | libfoo-libc5-dev| /usr/{lib,include}
I still have trouble with this. There is already a
libc5 | libfoo-dev| /usr/{lib,include}
for each libfoo out there. When people upgrade from 1.3->2.0, what's
*s
...
>based on | package name | library location
>
> libc6 | libfoo | /usr/lib/libfoo.so.
> libc5 | libfoo-libc5 | /usr/lib/libc5-compat/libfoo.so.
>
...
> based on | package name| hierarchy loc
Hi Folks!
The late discussion here on migration to libc6 indicates that a
statement on the requirements of library run time and development
packages is to be included in the policy manual. This is how I recall
the discussion we had about this topic some weeks ago. It might be
that I am a little b
4 matches
Mail list logo
