On Mon, 02 Jan 2012 16:18:23 -0500 Michael Orlitzky <mich...@orlitzky.com> wrote:
> On 01/02/2012 04:11 PM, Alan McKinnon wrote: > > 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. > > > > Requires time travel, not a solution! Eh? Did you read what I wrote? You don't have to go back and figure it all out all over again, "emerge -p <something>" tells you what needs to be emerged. Paste-edit that into a set file and Bob's your Auntie. What are you looking for here? Do you seek a magic way for portage to know what you intended and why you did what you did when you did it? Software can't do that. -- Alan McKinnnon alan.mckin...@gmail.com
