| 1 |
On Sun, 2004-01-18 at 18:42, Brad House wrote: |
| 2 |
> yes that would work, but drobbins already expressed a concern with |
| 3 |
> USE=livecd Since we base our livecds off of a stage3 which would |
| 4 |
> NOT have USE=livecd, we have to reemerge baselayout. I don't believe |
| 5 |
> catalyst is capable of reemerging the same package that already exists |
| 6 |
> on the system without hacking it up some, so the easier way around would |
| 7 |
> be to make everyone bump the baselayout -rN and resnap the portage tree |
| 8 |
> and make it depend on that version of baselayout. Just another |
| 9 |
> step which the whole point to catalyst was to have everything in portage |
| 10 |
> and easy to use so general users could create their own livecds with |
| 11 |
> their own apps, etc. |
| 12 |
|
| 13 |
Oh, and I never said you had to remerge baselayout - but come to think |
| 14 |
of it, you are right, it will have to be done so. But it will have to |
| 15 |
be done so anyhow. |
| 16 |
|
| 17 |
So I do propose that catalyst rather install livecd-functions.sh by |
| 18 |
itself, as it will: |
| 19 |
1) Not need a remerge |
| 20 |
2) Keep livecd-functions.sh seperate, so future fixes will not need |
| 21 |
a baselayout bump, but just an catalyst one. |
| 22 |
|
| 23 |
> It is a solution, just not the best at this point :/ |
| 24 |
> I still don't see the security concern though, but perhaps I'm |
| 25 |
> thick headed. |
| 26 |
> |
| 27 |
> > Ok, what about catalist install its own version of livecd-functions.sh |
| 28 |
> > for the moment, with the ebuild only when USE=livecd. We then change |
| 29 |
> > the bit for sourcing livecd-functions.sh in /sbin/rc to: |
| 30 |
> > |
| 31 |
> > -- |
| 32 |
> > --- rc-scripts-1.4.3.12p2/sbin/rc 2003-12-25 19:25:24.000000000 |
| 33 |
> > -0500 |
| 34 |
> > +++ rc-scripts-1.4.3.12p5/sbin/rc 2004-01-16 23:10:40.880824792 |
| 35 |
> > -0500 |
| 36 |
> > @@ -6,6 +6,7 @@ |
| 37 |
> > |
| 38 |
> > trap ":" INT QUIT TSTP |
| 39 |
> > source /sbin/functions.sh |
| 40 |
> > +[ -f /sbin/livecd-functions.sh ] && source /sbin/livecd-functions.sh |
| 41 |
> > umask 022 |
| 42 |
> > |
| 43 |
> > try() { |
| 44 |
> > @@ -163,6 +164,11 @@ |
| 45 |
> > -- |
| 46 |
> > |
| 47 |
> > Meaning any of the livecd changes will _only_ be available on a livecd, |
| 48 |
> > which cuts the uneeded overhead, and settles Paul's concerns? When |
| 49 |
> > USE=livecd then propagated, catalyst can then stop installing its own |
| 50 |
> > version ... |
| 51 |
> > |
| 52 |
> > |
| 53 |
> > -- |
| 54 |
> > Martin Schlemmer |
| 55 |
> > -- |
| 56 |
> > |
| 57 |
> > Martin Schlemmer |
| 58 |
> > Gentoo Linux Developer, Desktop/System Team Developer |
| 59 |
> > Cape Town, South Africa |
| 60 |
> > |
| 61 |
> > |
| 62 |
> > |
| 63 |
-- |
| 64 |
|
| 65 |
Martin Schlemmer |
| 66 |
Gentoo Linux Developer, Desktop/System Team Developer |
| 67 |
Cape Town, South Africa |
Archives