| 1 |
В Срд, 29/06/2011 в 07:53 +0100, Ciaran McCreesh пишет: |
| 2 |
> On Wed, 29 Jun 2011 02:47:36 -0400 |
| 3 |
> Mike Frysinger <vapier@g.o> wrote: |
| 4 |
> > > Both. There's code in Paludis that duplicates a bunch of that stuff |
| 5 |
> > > simply because I wasn't sure what I could and couldn't rely upon. |
| 6 |
> > |
| 7 |
> > the file should provide the classic e* output funcs that we've all |
| 8 |
> > grown to love, and are now enshrined in PMS. it has had other |
| 9 |
> > functions come and go over the years, but i think things have settled |
| 10 |
> > on just the output helpers. was there anything other than the output |
| 11 |
> > helpers you were interested in ? |
| 12 |
> |
| 13 |
> I seem to recall duplicating the colours stuff for Eselect too. But the |
| 14 |
> variable names seem to be different there, and the 'portageq' call |
| 15 |
> screws around with things, so perhaps by now things have diverged to the |
| 16 |
> extent that it's easier to just keep similar but different code around. |
| 17 |
|
| 18 |
Having single location for this functions allows system wide |
| 19 |
customization of colors... |
| 20 |
|
| 21 |
Personally I'd like to have this functions in separate package. What if |
| 22 |
we'll provide two tarballs from the single openrc sources, e.g. |
| 23 |
efunctions.tar.bz2 and openrc.tar.bz2, and correspodingly two packages? |
| 24 |
openrc tarbal will have code for efunctions included but its |
| 25 |
installation will be disabled in ebuild. This way we'll have full openrc |
| 26 |
sources for those who need it and in Gentoo we'll have separate package |
| 27 |
with efunctions for other packages to depend on. |
| 28 |
|
| 29 |
-- |
| 30 |
Peter. |
Archives