| 1 |
On Mon, 02 Jan 2012 16:18:23 -0500 |
| 2 |
Michael Orlitzky <michael@××××××××.com> wrote: |
| 3 |
|
| 4 |
> On 01/02/2012 04:11 PM, Alan McKinnon wrote: |
| 5 |
> > cocktail |
| 6 |
> > Neil's suggestion of sets sounds like what you want here. |
| 7 |
> > Unfortunately it only works smoothly on first emerge (later on you |
| 8 |
> > have to dig through dep graphs to find the full dep list): |
| 9 |
> > |
| 10 |
> > First run emerge -p to find all the packages that will be pulled in, |
| 11 |
> > and add the whole lot to a set with a clear name that indicates it's |
| 12 |
> > function. Then emerge that set. As you discover further deps you can |
| 13 |
> > manually add them to the set |
| 14 |
> > |
| 15 |
> > It's quite a lot of extra work and you have to remember to do it, |
| 16 |
> > but it has the benefit of being somewhat self-documenting, at least |
| 17 |
> > in terms of having a record of what set pulled a package in |
| 18 |
> > initially. |
| 19 |
> > |
| 20 |
> |
| 21 |
> Requires time travel, not a solution! |
| 22 |
|
| 23 |
|
| 24 |
Eh? Did you read what I wrote? |
| 25 |
|
| 26 |
You don't have to go back and figure it all out all over again, "emerge |
| 27 |
-p <something>" tells you what needs to be emerged. Paste-edit that |
| 28 |
into a set file and Bob's your Auntie. |
| 29 |
|
| 30 |
What are you looking for here? Do you seek a magic way for portage to |
| 31 |
know what you intended and why you did what you did when you did it? |
| 32 |
Software can't do that. |
| 33 |
|
| 34 |
-- |
| 35 |
Alan McKinnnon |
| 36 |
alan.mckinnon@×××××.com |
Archives