On Tue, 2005-01-18 at 20:07 +0000, Stuart Herbert wrote: > On Tuesday 18 January 2005 19:33, Ciaran McCreesh wrote: > > emerge -C kde-meta && emerge depclean > > > > Works fine, so long as you haven't ever done emerge /path/to/ebuild or > > installed packages which have conditional code based upon what the user > > has installed on their system (generally indicated by the has_version > > in global scope QA notice). > > Thanks for that. It's a shame that Portage doesn't know (and therefore can't > display) why the package was installed in the first place, but that's a minor > thing. > > What effect does this have on packages installed with the --oneshot option > (like, for example, everything mentioned in the GLSAs)?
--oneshot does not register the package in the world file. If the package had already been added to the world file by being merged by name, then it will still be in world. If the package was a dependency, then it will still be removed by a depclean, as it was *not* added to the world file and is still only there to satisfy the dependency. We you to not use --oneshot, then the package would not be removed, even if it was a dependency only. -- Chris Gianelloni Release Engineering - Operational/QA Manager Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
