From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NFPqS-0002Gy-Jr for garchives@archives.gentoo.org; Tue, 01 Dec 2009 10:20:33 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3FACAE066E for ; Tue, 1 Dec 2009 10:20:32 +0000 (UTC) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by pigeon.gentoo.org (Postfix) with ESMTP id DEA9BE073F for ; Tue, 1 Dec 2009 08:44:26 +0000 (UTC) Received: by fxm7 with SMTP id 7so4038288fxm.29 for ; Tue, 01 Dec 2009 00:44:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=IJgvAnY0b3qjLLlUOq1MGzUjijmUeSimHYT2BE59f+s=; b=ZpcBwPMHQoKgUE+fTFdeiZkOSJeyalLzfNF7rlKnIvlOBHsEHrN9d8coQG1GZNVxqh vdLvdin70T7IWD2bBC8Vsz8jbgk7/p1c1oecsZ/XMmaol/ZEGJ+ZDJggcAZcS4tcJvmB bPMlrgbEbF4XycOQ0NxkUA0kyPO/thsXxVjHI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=To3YBtoGRig/gmtoGuhuikSrDDOeUnlUKSCiaqxOT3O8N4uBz/yaudiCqzU++2LqgN kZzBiYadiSVDC3pV85VO7KzbuciFpqv6OrIgSeQ12Dv6Opsd9tpbuP4NwVVGqv9hasQF WazWmzgfX+Mn+u3EykUXLztuY8vBINis3Xcwg= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-embedded@lists.gentoo.org Reply-to: gentoo-embedded@lists.gentoo.org MIME-Version: 1.0 Received: by 10.223.15.11 with SMTP id i11mr797908faa.105.1259657066351; Tue, 01 Dec 2009 00:44:26 -0800 (PST) In-Reply-To: <20091130211241.27358.qmail@stuge.se> References: <166af1cf0911301024s61e229a6h9116c00ad84673e8@mail.gmail.com> <20091130211241.27358.qmail@stuge.se> From: Shinkan Date: Tue, 1 Dec 2009 09:44:06 +0100 Message-ID: <166af1cf0912010044l5ecf11ebkcc93dbbfe4603ebc@mail.gmail.com> Subject: Re: [gentoo-embedded] Cross Dev Tricks + Hardened questions To: gentoo-embedded@lists.gentoo.org Content-Type: multipart/alternative; boundary=0015174762a4fa8dd50479a6c3e8 X-Archives-Salt: 6cd6bddc-b5e9-4df0-8961-d121c7d5db25 X-Archives-Hash: 77425d2215b4b4ccbb0d5d54304ad900 --0015174762a4fa8dd50479a6c3e8 Content-Type: text/plain; charset=UTF-8 2009/11/30 Peter Stuge > > USE CATALYST! > > To do this you will create stage2, stage3 and stage4 spec files > (maybe also stage1, I'm not sure on that) for catalyst. It can > produce exactly what you want. > > Fine, I believe this would be controlled by USE flags for stage2 and > up. > > Please just start playing with the catalyst examples. I hope you will > quickly learn what they produce. > I already looked a lot into Catalyst but some points doesn't fit to my plans : - I have to use a profile if I want to specify things (for instance ports version) for base stage. I really don't want to build a profile because they're hard to maintain in a wide use scheme, and because that's overkill. - Catatalyst seems to build by substraction (I mean on livecd, it builds from a stage3, then unmerges and removes things). I want to build with additive steps (from nothing). - I want to be able to just emerge one new port or update one on a target, and with Catalyst I cant. I must rebuild all (yeah, cache is there but...), and I really need to build just one port on some cases. That's why I thought about a "build" directory built from my host with crossdev. Then I use this build env to build my target with gcc/libc I want. If I have to build just one port, I can use my build env for this target again. Since I choose what to build from nothing, I don't have to use profile to define what I put in my target or build. I don't break system by removing things. My build standard "make.conf" serves as usual, I have nothing more than a crossdev, a make.conf filling, and some emerge to a given root. That's what I want, but I don't know how to achieve this. If Catalyst can offer me this control, I would be glad to use it. -- Pierre. "Sometimes when I'm talking, my words can't keep up with my thoughts. I wonder why we think faster than we speak. Probably so we can think twice." - Bill Watterson --0015174762a4fa8dd50479a6c3e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
2009/11/30 Peter Stuge <= ;peter@stuge.se>

USE CATALYST!

To do this you will create stage2, stage3 and stage4 spec files
(maybe also stage1, I'm not sure on that) for catalyst. It can
produce exactly what you want.

Fine, I believe this would be controlled by USE flags for stage2 and<= br>
up.

Please just start playing with the catalyst examples. I hope you will=
quickly learn what they produce.

I already looked = a lot into Catalyst but some points doesn't fit to my plans :
- I ha= ve to use a profile if I want to specify things (for instance ports version= ) for base stage. I really don't want to build a profile because they&#= 39;re hard to maintain in a wide use scheme, and because that's overkil= l.
- Catatalyst seems to build by substraction (I mean on livecd, it builds fr= om a stage3, then unmerges and removes things). I want to build with additi= ve steps (from nothing).
- I want to be able to just emerge one new port= or update one on a target, and with Catalyst I cant. I must rebuild all (y= eah, cache is there but...), and I really need to build just one port on so= me cases.

That's why I thought about a "build" directory built from= my host with crossdev. Then I use this build env to build my target with g= cc/libc I want. If I have to build just one port, I can use my build env fo= r this target again.
Since I choose what to build from nothing, I don't have to use profile = to define what I put in my target or build. I don't break system by rem= oving things.
My build standard "make.conf" serves as usual, I= have nothing more than a crossdev, a make.conf filling, and some emerge to= a given root.

That's what I want, but I don't know how to achieve this.
If= Catalyst can offer me this control, I would be glad to use it.


--
Pierre.
"Sometimes when I'm talking, my word= s can't keep up with my thoughts. I wonder why we think faster than we = speak. Probably so we can think twice." - Bill Watterson
--0015174762a4fa8dd50479a6c3e8--