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