deface wrote: > It sounds like the mistake was on your hand. baselayout isn't udated > as often, unless you are ~**. the missing files are from any > baselayout, not just the version you are stating. > > *** WARNING *** Depclean may break link level dependencies. Thus, it is > *** WARNING *** recommended to use a tool such as `revdep-rebuild` (from > *** WARNING *** app-portage/gentoolkit) in order to detect such > breakage. > *** WARNING *** > *** WARNING *** Also study the list of packages to be cleaned for any > obvious > *** WARNING *** mistakes. Packages that are part of the world set > will always > *** WARNING *** be kept. They can be manually added to this set with > *** WARNING *** `emerge --noreplace <atom>`. Packages that are > listed in > *** WARNING *** package.provided (see portage(5)) will be removed by > *** WARNING *** depclean, even if they are part of the world set. > *** WARNING *** > *** WARNING *** As a safety measure, depclean will not remove any > packages > *** WARNING *** unless *all* required dependencies have been > resolved. As a > *** WARNING *** consequence, it is often necessary to run > *** WARNING *** `emerge --update --newuse --deep world` prior to > depclean. > > Plenty of warning there. Not recommended to --depclean. UNLESS > absolutely necessary. > > deface > > >
Isn't baselayout part of system? Wouldn't --depclean leave that installed? Something sounds . . . fishy. I run --depclean and I don't recall it ever removing something in system. That said, always add a -p or -a to that thing. It can boo boo and remove something you need if you are not careful. I removed a kde thing once. No GUI for a bit. Dale :-) :-) -- gentoo-user@lists.gentoo.org mailing list
