From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
	by nuthatch.gentoo.org with esmtp (Exim 4.54)
	id 1FMANz-0005NZ-2J
	for garchives@archives.gentoo.org; Wed, 22 Mar 2006 20:56:55 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
	by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k2MKuQiJ002322;
	Wed, 22 Mar 2006 20:56:26 GMT
Received: from web30215.mail.mud.yahoo.com (web30215.mail.mud.yahoo.com [68.142.201.228])
	by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k2MKuPJI025050
	for <gentoo-catalyst@lists.gentoo.org>; Wed, 22 Mar 2006 20:56:25 GMT
Received: (qmail 23724 invoked by uid 60001); 22 Mar 2006 20:56:24 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=qQ3fuzrm0iX0hlBZb0v6R4I9a5qzDAw316Z+VetdTG49/2Kr5UdYZRSn+G2IfpF+ZJsRdb9x6/kSHDNkui5Zrfklz9GcqaQfM1OD+xGuW1+Oy/pCImjONSBSQbij5SR4oD6Fa+RTugiFAyOoXBAoIrXaRxoSa5iTjK3XP4u4wvE=  ;
Message-ID: <20060322205624.23722.qmail@web30215.mail.mud.yahoo.com>
Date: Wed, 22 Mar 2006 12:56:24 -0800 (PST)
From: Tod Herman <todw1fd@yahoo.com>
Subject: Re: [gentoo-catalyst] custom motd gets blanked
To: gentoo-catalyst@lists.gentoo.org
In-Reply-To: <1143059806.9002.41.camel@cgianelloni.nuvox.net>
Precedence: bulk
List-Post: <mailto:gentoo-catalyst@lists.gentoo.org>
List-Help: <mailto:gentoo-catalyst+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-catalyst+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-catalyst+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-catalyst.gentoo.org>
X-BeenThere: gentoo-catalyst@gentoo.org
Reply-to: gentoo-catalyst@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Archives-Salt: 925698da-8b89-4a8c-ae28-698179ecc318
X-Archives-Hash: 884c1b8f1a76d572232dfcc78a89da1c

Geez.  Been thru the spec files.  Really do try and solve what I can myself before bothering others.  Also read thru all the scripts when seeking a solution.  Clarity is relative.  And not everything in the example spec files is correct.  Wasn't calling you an ass.  If I wished to, I would have done so clearly.  Have a good day.  

----- Original Message ----
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Sent: Wednesday, March 22, 2006 3:36:46 PM
Subject: Re: [gentoo-catalyst] custom motd gets blanked

On Wed, 2006-03-22 at 12:17 -0800, Tod Herman wrote:
> Everyone has to start somewhere.  And without warnings up front in any kind of documentation to the contrary, people are going to try to take the easiest path to get a desired result.  Learning to use the tool correctly, and in a way "sanctioned" by those intimately involved in its creation, isn't exactly easy.  Of course, now, having been spanked for my attempts at catalyst glory, i will go back and try and do it all the "right" way.   Thanks just the same Chris.

*sigh*

I wasn't trying to be an ass or anything.  I was merely pointing you in
the right direction.  Besides, it is pretty clear in the example spec
files installed with catalyst.  You know, the ones that the catalyst
ebuild tells you to read.  Yeah, those...

# This option controls quite a bit of catalyst internals and sets up
several
# defaults.  Each type behaves slightly differently and is explained
below.
# gentoo-release-minimal - This creates an official minimal InstallCD.
# gentoo-release-universal - This creates an official universal
InstallCD.
# gentoo-release-livecd - This creates an official LiveCD environment.
# gentoo-gamecd - This creates an official Gentoo GameCD.
# generic-livecd - This should be used for all non-official media.
# example:
# livecd/type: gentoo-release-minimal
livecd/type:

Now, as you can probably guess, your CD would be "non-official media".

I understand that catalyst is a complex tool to learn, but trying to
make it sound like we didn't try to document this is simply unfair to
those of us that spend our time not only writing the tool, but also
taking the time to write out all of the documentation.  It really isn't
appreciated when you try to lay the onus of blame on the developers when
they've tried their best to make it clear how to proceed.

At any rate, the *real* goal here is to have taught you, and I think we
have.  I apologize if you feel that this wasn't done in the best manner,
but there's not much else that we can do other than provide
documentation explaining the options, which we have.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux



-- 
gentoo-catalyst@gentoo.org mailing list