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 <[EMAIL PROTECTED]> To: [email protected] 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 -- [EMAIL PROTECTED] mailing list
