Summary: | sys-libs/readline libreadline.so.4 is deleted when upgrading to 5.0-r2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rune Schjellerup <olberd> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rune Schjellerup
2005-08-04 00:18:55 UTC
you dont just arbitrarily SLOT packages readline-4 and readline-5 have no API changes so packages build fine against either, the ABI just changed the readline-5 ebuild should copy over the previous libreadline.so.4 library for you Well, then don't slot the package.
>the readline-5 ebuild should copy over the
>previous libreadline.so.4 library for you
That might be true, but the libreadline.so.4 is still deleted when readline-4
ebuild is unmerged,
and this is what I have a problem with.
(In reply to comment #2) > That might be true, but the libreadline.so.4 is still deleted when readline-4 > ebuild is unmerged, > and this is what I have a problem with. No, it is not. <snip> # Backwards compatibility #29865 if [[ -e ${ROOT}/$(get_libdir)/libreadline.so.4 ]] ; then cp -a "${ROOT}"/$(get_libdir)/libreadline.so.4* "${D}"/$(get_libdir)/ touch "${D}"/$(get_libdir)/libreadline.so.4* fi </snip> yeah, you're gonna have to provide some usage info because the ebuild looks correct and it upgraded my readline-4 to readline-5 systems just fine ... |