1 |
On Wed, Jun 29, 2011 at 03:49:13PM +0400, Peter Volkov wrote: |
2 |
> В Срд, 29/06/2011 в 07:53 +0100, Ciaran McCreesh пишет: |
3 |
> > On Wed, 29 Jun 2011 02:47:36 -0400 |
4 |
> > Mike Frysinger <vapier@g.o> wrote: |
5 |
> > > > Both. There's code in Paludis that duplicates a bunch of that stuff |
6 |
> > > > simply because I wasn't sure what I could and couldn't rely upon. |
7 |
> > > |
8 |
> > > the file should provide the classic e* output funcs that we've all |
9 |
> > > grown to love, and are now enshrined in PMS. it has had other |
10 |
> > > functions come and go over the years, but i think things have settled |
11 |
> > > on just the output helpers. was there anything other than the output |
12 |
> > > helpers you were interested in ? |
13 |
> > |
14 |
> > I seem to recall duplicating the colours stuff for Eselect too. But the |
15 |
> > variable names seem to be different there, and the 'portageq' call |
16 |
> > screws around with things, so perhaps by now things have diverged to the |
17 |
> > extent that it's easier to just keep similar but different code around. |
18 |
> |
19 |
> Having single location for this functions allows system wide |
20 |
> customization of colors... |
21 |
> |
22 |
> Personally I'd like to have this functions in separate package. What if |
23 |
> we'll provide two tarballs from the single openrc sources, e.g. |
24 |
> efunctions.tar.bz2 and openrc.tar.bz2, and correspodingly two packages? |
25 |
> openrc tarbal will have code for efunctions included but its |
26 |
> installation will be disabled in ebuild. This way we'll have full openrc |
27 |
> sources for those who need it and in Gentoo we'll have separate package |
28 |
> with efunctions for other packages to depend on. |
29 |
|
30 |
That is similar to what I'm looking at doing with openrc. What I'm |
31 |
thinking if we go that route is that openrc will have a use flag, |
32 |
"core", or something similar which will install enough of openrc to make |
33 |
those functions available. I am opposed to two separate packages; I |
34 |
think that is a lot more work than necessary. |
35 |
|
36 |
The disadvantage is that functions.sh is not a simple script; most of |
37 |
the functions are actually part of /sbin/rc which is a multi call binary, |
38 |
so I'll need to make sure the unnecessary functionality is disabled in |
39 |
the binary as well. |
40 |
|
41 |
William |