| 1 |
On Wed, Jun 29, 2011 at 02:53, Ciaran McCreesh wrote: |
| 2 |
> On Wed, 29 Jun 2011 02:47:36 -0400 Mike Frysinger wrote: |
| 3 |
>> > Both. There's code in Paludis that duplicates a bunch of that stuff |
| 4 |
>> > simply because I wasn't sure what I could and couldn't rely upon. |
| 5 |
>> |
| 6 |
>> the file should provide the classic e* output funcs that we've all |
| 7 |
>> grown to love, and are now enshrined in PMS. it has had other |
| 8 |
>> functions come and go over the years, but i think things have settled |
| 9 |
>> on just the output helpers. was there anything other than the output |
| 10 |
>> helpers you were interested in ? |
| 11 |
> |
| 12 |
> I seem to recall duplicating the colours stuff for Eselect too. But the |
| 13 |
> variable names seem to be different there, and the 'portageq' call |
| 14 |
> screws around with things, so perhaps by now things have diverged to the |
| 15 |
> extent that it's easier to just keep similar but different code around. |
| 16 |
|
| 17 |
the env var names should be the same as they've always been, but this |
| 18 |
wasnt generally something i focused on. i dont think PMS does either. |
| 19 |
although in looking and some scripts which use it, they sometimes |
| 20 |
leverage the env vars directly, so i guess encoding it should be |
| 21 |
simple enough. just documenting what has always been. |
| 22 |
|
| 23 |
openrc's functions.sh doesnt call portageq, so i'm not sure what |
| 24 |
you're referring to there. |
| 25 |
|
| 26 |
the func names and behavior between openrc shouldnt have diverged from |
| 27 |
what portage/PMS does. if it has, probably should open a bug for it. |
| 28 |
-mike |
Archives