On Mon, Jan 2, 2012 at 12:47 PM, Mark Knecht <markkne...@gmail.com> wrote: > On Mon, Jan 2, 2012 at 9:39 AM, Michael Orlitzky <mich...@orlitzky.com> wrote: >> On 01/02/12 12:06, Michael Mol wrote: >>> >>> That's the purpose of the "emerge -p" step. Presumably, you would see >>> that there's a package in the list that you're not comfortable with >>> removing, you'd decide you didn't want it removed, and you'd add it >>> back to your world set. >> >> Yeah, I'm not sure I can remove any of them. The only way I see to >> determine what's necessary at this point is to remove it and see if >> stuff breaks. >> > > Again, 'equery depends' will tell you if any package locatable through > the @world hierarchy needs the package. No need to uninstall anything > to do that level of investigation. revdep-rebuild -I is also useful, > although more historically than now.
The problem is that he won't know which atoms in his current world set are necessarily depended upon by other packages vs the ones which are requested by his customers' request. (Portage knows nothing about his customers' requests; it only knows he installed packages at one point or another.) [snip] -- :wq
