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 1Qh22Q-0008Ui-Id for garchives@archives.gentoo.org; Wed, 13 Jul 2011 16:11:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9A32821C07D for ; Wed, 13 Jul 2011 16:11:49 +0000 (UTC) Received: from mail1.nippynetworks.com (mail1.nippynetworks.com [91.220.24.129]) by pigeon.gentoo.org (Postfix) with ESMTP id 3345321C07D for ; Wed, 13 Jul 2011 15:49:02 +0000 (UTC) Received: from localhost (mail1.nippynetworks.com [127.0.0.1]) by mail1.nippynetworks.com (Postfix) with ESMTP id CDE783403C5 for ; Wed, 13 Jul 2011 16:49:00 +0100 (BST) X-Virus-Scanned: amavisd-new at nippynetworks.com Received: from mail1.nippynetworks.com ([127.0.0.1]) by localhost (mail1.nippynetworks.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id o0c4YkbgXyGn for ; Wed, 13 Jul 2011 16:49:00 +0100 (BST) Received: from Ed-Wildgooses-MacBook-Pro.local (office.nippynetworks.com [212.69.49.94]) (Authenticated sender: edward@wildgooses.com) by mail1.nippynetworks.com (Postfix) with ESMTPSA id 6779A34039F for ; Wed, 13 Jul 2011 16:49:00 +0100 (BST) Message-ID: <4E1DBE6B.9020607@wildgooses.com> Date: Wed, 13 Jul 2011 16:48:59 +0100 From: Ed W User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 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 To: gentoo-embedded@lists.gentoo.org Subject: Re: [gentoo-embedded] generating root file systems References: <4E1D7970.7080404@wildgooses.com> In-Reply-To: X-TagToolbar-Keys: D20110713164859960 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: 28dab2329f3bd0c729a99e24d7254727 > Well, catalyst was designed to build a gentoo image. I want to build > embedded images that have nothing gentoo specific about them. No > portage, no python, no eselect or anything else like that. Actually (and speaking with no real experience), I believe it can build exactly that... However, it's big and complicated as solutions go (also there is the tool from Funtoo) >> Patching ebuilds in mind: I have been experimenting with >> /etc/portage/patches and also the bashrc for broad patching, eg where >> some long standing patch or config customisation is necessary (eg delete >> some openrc file which makes no sense, or customise some udev config, >> etc) > I've never heard of that file, '/etc/portage/patches', and can't find it > in man portage. Just create /etc/portage/patches/net-dns/dnscache/somepatch.patch In theory the docs said that if the file was called dnscache-1.2.3-mypatch.patch, then it would only apply to that version number, but for me it seems all patches are applied (I rename them to exclude them) Additionally the hooks for each stage of portage are accessible from /etc/portage/bashrc > There always is a learning curve for embedded and it will be impossible > to support every single configuration for every single board. Basically > my plan was to try to logically split all the steps in making a > filesystem image and put them into a clear well documented bash script, Sure - actually I just have a base file called "mod", that includes your "recipe" file and then it calls functions: mount_deps(), build(), target(), unmount_deps() from the recipe file. It's the provider of the recipe's job to fill in each of those functions It means I can call "./mod build 0.1" repeatedly (the number is the package version number) until I'm happy and then call "./mod target 0.1", etc > I can drop what a have so far into a git repo and we can go from there > taking the best from each of our scripts. Do you want to make the repo > or should I? I think you should knock up some repo (probably github is a good choice because it's so easy to fork). If you are interested I will email over some samples of my small scripts and you can see if they are interesting to work into your basic environment? Cheers Ed W