On Mon, 02 Jan 2012 11:33:43 -0500 Michael Orlitzky <mich...@orlitzky.com> wrote:
> On 01/02/2012 11:16 AM, Michael Mol wrote: > >> > >> Fine for your home PC, doesn't cut it on servers. I have the > >> following in one of my world files: > >> > >> dev-php/PEAR-Mail > >> dev-php/PEAR-Mail_Mime > >> dev-php/PEAR-PEAR > >> dev-php/PEAR-Structures_Graph > >> > >> which of those do I want? At least one of them was installed to > >> support a customer's custom PHP application. Maybe all of them > >> were and they all belong in world. No one knows, this server is > >> older than the current --update behavior. > >> > >> So which ones can I remove? > >> > >> Solutions involving time travel and/or losing customers will be > >> disqualified. > > > > Make a backup copy of your world file. > > > > 1a. Remove those four lines. > > 2a. emerge -p --depclean > > 3a. Did any of those show up in the to-be-removed set? Add them > > back. > > > > Alternately: > > 1b. emerge -pev --tree --with-bdeps=y @world > > 2b Find those packages in the output. The tree form of the display > > will help you see if anything is depending on them. > > 3b. If anything is depending on them, you should be able to safely > > remove them from your world file. I'd follow up with the 1a, 2a, 3a > > solution to be sure. > > > > Sorry, but these won't work. > > Let's say that dev-php/PEAR-Mail_Mime has a dependency on > dev-php/PEAR-Mail, but I have a customer who needs dev-php/PEAR-Mail > for a contact form. > > Following your process, I would remove dev-php/PEAR-Mail from my > world file. If I ever remove dev-php/PEAR-Mail_Mime, depclean will > remove PEAR-Mail and break the guy's site. > cocktail Neil's suggestion of sets sounds like what you want here. Unfortunately it only works smoothly on first emerge (later on you have to dig through dep graphs to find the full dep list): First run emerge -p to find all the packages that will be pulled in, and add the whole lot to a set with a clear name that indicates it's function. Then emerge that set. As you discover further deps you can manually add them to the set It's quite a lot of extra work and you have to remember to do it, but it has the benefit of being somewhat self-documenting, at least in terms of having a record of what set pulled a package in initially. -- Alan McKinnnon alan.mckin...@gmail.com
