| 1 |
On Wed, Oct 29, 2008 at 10:23 PM, Andrey Vul <andrey.vul@×××××.com> wrote: |
| 2 |
> But I usually use emerge -p > file in order to see the difference in |
| 3 |
> dependencies from testing USE flags. |
| 4 |
> I would always choose -pN over -aN. |
| 5 |
> |
| 6 |
> Where's the portage to-do list? |
| 7 |
> If you can find it, add these two items: |
| 8 |
> fix the uname |
| 9 |
> add pager support for -p, -a, -t |
| 10 |
|
| 11 |
Well, I didn't find it with the miserably little effort I put into |
| 12 |
looking... so instead, I wrote up a quick hack to emerge to implement |
| 13 |
use of a pager any time the internal display() function is called. I |
| 14 |
made the mistake of writing it against the 'stable' version of |
| 15 |
portage, though... so I'll be (hopefully) porting it over to Portage |
| 16 |
2.2_rc12 (the newest my current state of laziness allows on my amd64 |
| 17 |
machine). Any chance anyone here's a bit more skilled with python than |
| 18 |
I am and would want to remind me of all the error checking I left out? |
| 19 |
After I get a patch handy, at least... |
| 20 |
|
| 21 |
As for the 'fix the uname' bit... I haven't had a chance to dig |
| 22 |
through the changelogs to see the who/when/why of the change that made |
| 23 |
it what it is now, and whether (as was clarified as likely in the |
| 24 |
related thread here) the current output is what's "intended." |
| 25 |
|
| 26 |
-- |
| 27 |
Poison [BLX] |
| 28 |
Joshua M. Murphy |
Archives