When emerging kde-xxxx-meta or fortune-mod-all (examples), any needed dependencies are automatically emerged. However, the unmerge feature will NOT unmerge dependencies. Both kde and fortune-mod-all use RDEPEND. I cannot see a way to unmerge all components other than one by one. Is this a defect in emerge or the way the ebuild was constructed? Unmerging kde-xxxx-meta simply removes the meta file. That file is the only one that goes into the world file. Seems like the components that are emerged should be in world too. Reproducible: Always Steps to Reproduce: 1. emerge fortune-mod-all 2. emerge --unmerge fortune-mod-all 3. equery f fortune-mod-dubya (for example) Actual Results: dubya is still there. Expected Results: dubya should not be there I believe care should be taken when emerge brings in RDEPEND files so that they can be removed by the parent program. OR ebuild should be crafted in such a way that dependencies are clearly noted. Right now, there is no clear way to get rid of a meta file's components. The only workaround I can see is to cat the ebuild and unmerge each RDEPEND manually. I also think that RDEPEND files emerged with a meta type file should go into world too. Certainly not a showstopper, but an item worth looking at. Marking minor since this may be by design.
Use emerge --N world and then emerge --depclean. --unmerge will not clean meta builds, that is depcleans job.
thx. But if the dependencies are RDEPEND, will they still be picked up? That's why I suggested it might be a design problem with the ebuild. Would it be different if it was marked DEPEND instead? Then I could see depclean working. Anyway, just thought I'd bring it up.
