From: Martin Schlemmer <azarah@gentoo.org>
To: Brad House <brad_mssw@gentoo.org>
Cc: gentoo-releng@lists.gentoo.org, John Davis <zhen@gentoo.org>,
Gentoo-Base-System <base-system@gentoo.org>
Subject: Re: [gentoo-releng] Re: baselayout changes for livecds
Date: Sun, 18 Jan 2004 19:34:00 +0200 [thread overview]
Message-ID: <1074447240.8472.215.camel@nosferatu.lan> (raw)
In-Reply-To: <64982.68.105.173.45.1074444131.squirrel@mail.mainstreetsoftworks.com>
[-- Attachment #1: Type: text/plain, Size: 2432 bytes --]
On Sun, 2004-01-18 at 18:42, Brad House wrote:
> yes that would work, but drobbins already expressed a concern with
> USE=livecd Since we base our livecds off of a stage3 which would
> NOT have USE=livecd, we have to reemerge baselayout. I don't believe
> catalyst is capable of reemerging the same package that already exists
> on the system without hacking it up some, so the easier way around would
> be to make everyone bump the baselayout -rN and resnap the portage tree
> and make it depend on that version of baselayout. Just another
> step which the whole point to catalyst was to have everything in portage
> and easy to use so general users could create their own livecds with
> their own apps, etc.
Oh, and I never said you had to remerge baselayout - but come to think
of it, you are right, it will have to be done so. But it will have to
be done so anyhow.
So I do propose that catalyst rather install livecd-functions.sh by
itself, as it will:
1) Not need a remerge
2) Keep livecd-functions.sh seperate, so future fixes will not need
a baselayout bump, but just an catalyst one.
> It is a solution, just not the best at this point :/
> I still don't see the security concern though, but perhaps I'm
> thick headed.
>
> > Ok, what about catalist install its own version of livecd-functions.sh
> > for the moment, with the ebuild only when USE=livecd. We then change
> > the bit for sourcing livecd-functions.sh in /sbin/rc to:
> >
> > --
> > --- rc-scripts-1.4.3.12p2/sbin/rc 2003-12-25 19:25:24.000000000
> > -0500
> > +++ rc-scripts-1.4.3.12p5/sbin/rc 2004-01-16 23:10:40.880824792
> > -0500
> > @@ -6,6 +6,7 @@
> >
> > trap ":" INT QUIT TSTP
> > source /sbin/functions.sh
> > +[ -f /sbin/livecd-functions.sh ] && source /sbin/livecd-functions.sh
> > umask 022
> >
> > try() {
> > @@ -163,6 +164,11 @@
> > --
> >
> > Meaning any of the livecd changes will _only_ be available on a livecd,
> > which cuts the uneeded overhead, and settles Paul's concerns? When
> > USE=livecd then propagated, catalyst can then stop installing its own
> > version ...
> >
> >
> > --
> > Martin Schlemmer
> > --
> >
> > Martin Schlemmer
> > Gentoo Linux Developer, Desktop/System Team Developer
> > Cape Town, South Africa
> >
> >
> >
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-18 17:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 4:23 [gentoo-releng] baselayout changes for livecds Brad House
2004-01-17 10:26 ` [gentoo-releng] " Paul de Vrieze
2004-01-17 16:28 ` Brad House
2004-01-17 16:51 ` Pieter Van den Abeele
2004-01-17 17:06 ` Brad House
2004-01-17 17:34 ` Pieter Van den Abeele
2004-01-17 18:29 ` Paul de Vrieze
2004-01-17 20:23 ` Martin Schlemmer
2004-01-17 20:57 ` Brad House
2004-01-18 8:06 ` Martin Schlemmer
2004-01-17 22:11 ` Martin Schlemmer
2004-01-17 22:32 ` John Davis
[not found] ` <1074380018.8472.9.camel@nosferatu.lan>
2004-01-18 5:24 ` Daniel Robbins
2004-01-18 8:24 ` Martin Schlemmer
2004-01-18 16:42 ` Brad House
2004-01-18 17:30 ` Martin Schlemmer
2004-01-18 17:40 ` Brad House
2004-01-18 17:34 ` Martin Schlemmer [this message]
2004-01-19 21:39 ` Daniel Robbins
2004-01-19 21:47 ` Brad House
2004-01-20 4:40 ` Martin Schlemmer
2004-01-20 19:20 ` Daniel Robbins
2004-01-21 19:12 ` Martin Schlemmer
2004-01-23 18:07 ` Martin Schlemmer
2004-01-18 0:47 ` Daniel Robbins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074447240.8472.215.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=base-system@gentoo.org \
--cc=brad_mssw@gentoo.org \
--cc=gentoo-releng@lists.gentoo.org \
--cc=zhen@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox