1 |
> |
2 |
> Well, you cannot expect anything to just fall into place if you drop |
3 |
> this on me right now, and say 'it have to be fixed right now'. How |
4 |
> long have work for catalyst been going? Why didn't you involve me |
5 |
> sooner if you _knew_ there would be baselayout changes? |
6 |
|
7 |
This was all just thrown on me last week, and with the release |
8 |
pending, I worked my ass off to get it all done. Baselayout was |
9 |
a very small part of all of that. Drobbins did a good job getting |
10 |
catalyst done, but a lot was left up to me with the rest of the |
11 |
system, and tweaking some things in catalyst to be more friendly. |
12 |
Please don't act like it's just you stressed for time, you have no |
13 |
clue. I've worked more on Gentoo this week than I have my normal |
14 |
job. I don't know how I could have possibly notified you sooner. |
15 |
|
16 |
> |
17 |
> I already stepped back a bit, but I do _not_ see why the livecd stuff |
18 |
> should be overhead for all users, if it will be like 1 out of a 1000 |
19 |
> times actually for startups out there. Is it _really_ that much to |
20 |
> ask catalyst to just install /sbin/livecd-functions.sh if not present |
21 |
> at the end of stage3 unpack? |
22 |
|
23 |
Yes, we can make catalyst distribute that, but it's not organized |
24 |
to do that at all, catalyst is really only meant to distribute what |
25 |
is in a portage tree. Which is the opposite mentality from the previous |
26 |
livecd scripts. Again, it's hackish, and if I remember correctly, |
27 |
drobbins specifically forbids doing that. So we'd have to make a |
28 |
baselayout-livecd.ebuild or something to keep it in line. |
29 |
|
30 |
At this point though, I'm stepping back. I've provided the necessary |
31 |
changes, it's up to someone else to determine how to use and distribute |
32 |
them. I'm not a fan of bureaucracy, and don't deal with it well. |
33 |
|
34 |
-Brad |
35 |
|
36 |
-- |
37 |
gentoo-releng@g.o mailing list |