| Summary: | kde4.eclass conflicts with old KDE3 packages from overlays | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Fabio Rossi <rossi.f> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
It would only block KDE3 packages if you wanted to emerge the same package name in :3 and :4 - like e.g. kate:3 besides kate:4. But I guess no one really wants that, or am I missing something? In the reverse case of having installed KDE3 and some apps using KDE4 libs then you need to have installed the same package for both KDE3 and KDE4, for instance I have $ which -a kdesu /usr/bin/kdesu /usr/kde/3.5/bin/kdesu The apps are installed in different paths so there is no conflict. Without the suggested change in the kde4.eclass it's not possible to have both installed. I guess the blocker was introducted after having renamed the category name for the KDE4 packages. From the point of view of the official plain portage I guess there are no problems because KDE3 is not anymore in the tree |
I have installed a few old KDE3 apps from overlay kde-sunset. In the past the category of a few packages has been changed from kde-base to kde-apps and the kde4.eclass includes an automatic blocker: if [[ ${CATEGORY} == kde-apps ]]; then kderdepend+=" !kde-base/${PN}" fi which is blocking the old KDE3 packages. Would it be possible to change the restriction to only KDE4 packages putting a slot operator? if [[ ${CATEGORY} == kde-apps ]]; then kderdepend+=" !kde-base/${PN}:4" fi