1 |
On Tue, 2007-11-06 at 08:03 +0000, Ciaran McCreesh wrote: |
2 |
> On Tue, 06 Nov 2007 07:40:20 +0000 |
3 |
> Roy Marples <uberlord@g.o> wrote: |
4 |
> > On Tue, 2007-11-06 at 07:12 +0000, Ciaran McCreesh wrote: |
5 |
> > > Except it won't, because ebuilds require bash regardless of which |
6 |
> > > package manager is being used. If you want to change that you'll |
7 |
> > > have to rewrite the entire tree. |
8 |
> > |
9 |
> > Az once said near enough the same thing about baselayout. And that's |
10 |
> > your view, your entitled to it, but it is not my view. Change a little |
11 |
> > bit here, a little bit there. Slowly does it. |
12 |
> |
13 |
> It's not a view. It's a simple fact. |
14 |
|
15 |
It's my considered opinion that it's a view. |
16 |
You are free to call it what you like. |
17 |
|
18 |
> > Yes, I know that a fair chunk of the tree will need a re-write, just |
19 |
> > in the same way that the init scripts got a re-write. It will take |
20 |
> > time, it will not happen magically over night. To think overwise is |
21 |
> > foolish :) |
22 |
> |
23 |
> How many lines of code are in baselayout? How many in the tree? |
24 |
> |
25 |
> Pushing for non-bash for ebuilds is pointless. The cost of using bash is |
26 |
> tiny; the cost of not using bash is huge. |
27 |
|
28 |
Size of baselayout compared to the tree is small vs huge. But unlike |
29 |
baselayout, the ebuilds themselves should be relatively easy as they |
30 |
don't normally use bash specific features [1]. The real work is in the |
31 |
eclasses which make extensive use of bash specific features, such as |
32 |
arrays. A quick look at the dir shows that there's probably a similar |
33 |
number of eclasses to the number of init scripts installed by ebuilds. |
34 |
|
35 |
[1] The one expection being ${var//foo/var} which is used a fair bit. It |
36 |
could also be argued that versionator should be used more which oddly |
37 |
enough should also reduce the use of this bashism. |
38 |
|
39 |
Thanks |
40 |
|
41 |
Roy |
42 |
|
43 |
-- |
44 |
gentoo-dev@g.o mailing list |