public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Daniel Robbins <drobbins@gentoo.org>
Cc: Brad House <brad_mssw@gentoo.org>,
	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: Tue, 20 Jan 2004 06:40:02 +0200	[thread overview]
Message-ID: <1074573602.8472.246.camel@nosferatu.lan> (raw)
In-Reply-To: <1074548358.20759.2.camel@music.gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

On Mon, 2004-01-19 at 23:39, Daniel Robbins wrote:
> On Sun, 2004-01-18 at 10:34, Martin Schlemmer wrote:
> > 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.
> 
> OK, let's support a USE="livecd" but *only* for baselayout at this point
> (don't want it to be used for other ebuilds for 2004.0.) If
> USE="livecd", then livecd-functions.sh gets installed. And you can add a
> "[ -f livecd-functions.sh ] && source" conditional.
> 
> Will that work for everyone? Please? :)
> 

Yep.  Sorry, but I am just anti-bloat in baselayout =)  Brad do have a
point though - can catalyst remerge baselayout?  Or can it rather
install livecd-functions.sh.  I am not sure about the 'hack' level that
will be (as Brad keeps calling it), but then I have not had a chance to
look at catalyst as of yet.


-- 

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 --]

  parent reply	other threads:[~2004-01-20  4:36 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
2004-01-19 21:39               ` Daniel Robbins
2004-01-19 21:47                 ` Brad House
2004-01-20  4:40                 ` Martin Schlemmer [this message]
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=1074573602.8472.246.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=base-system@gentoo.org \
    --cc=brad_mssw@gentoo.org \
    --cc=drobbins@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