As a pure paludis user, I want to uninstall portage. But explicit dependencies in some packages prevent deinstallation: # paludis --uninstall sys-apps/portage --with-unused-dependencies -p Building unmerge list... done These packages will be uninstalled: * app-admin/python-updater-0.6-r1::installed requires <sys-apps/portage-2.1.6.7::installed> * app-portage/gentoolkit-0.2.4.2-r1::installed requires <sys-apps/portage-2.1.6.7::installed> * app-portage/udept-0.5.99.0.2.95-r1::installed requires <sys-apps/portage-2.1.6.7::installed> * dev-java/sun-jdk-1.6.0.11::installed requires <sys-apps/portage-2.1.6.7::installed> * dev-libs/soprano-2.2.1::installed requires <sys-apps/portage-2.1.6.7::installed> * sys-libs/glibc-2.9_p20081201-r1::installed requires <sys-apps/portage-2.1.6.7::installed> * sys-apps/portage-2.1.6.7::installed Total: 1 package and 6 errors Reproducible: Always Steps to Reproduce: Actual Results: It's impossible to uninstall portage (even when forced, next update would pull it in again). Expected Results: Since there is virtual/portage, it should be sufficient to have any package manager installed, so with paludis installed, I should be able to uninstall portage.
Uhm no. apart from glibc, which depends on a new enough version of portage, all others you listed actually use portage.
Soprano? sun-jdk? Use portage? So how do they work on other distributions?
udept and gentoolkit I have uninstalled. Regarding python-updater: We have a circular dep here (python-updater->portage->python->python-updater).
Is it allowed to depend on a package manager? Shouldn't this be done through EAPIs? If so, then this bug report should be made a tracker and other bugs for the individual packages should be reported (or else we'll be dozens of comments removed from our target before anything will be ever done).
*** This bug has been marked as a duplicate of bug 162516 ***
