From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Cc: "Alon Keren" <alon.keren@gmail.com>
Subject: Re: [gentoo-user] Creating a LFS system with Portage
Date: Tue, 19 Sep 2006 13:33:40 -0700 [thread overview]
Message-ID: <7573e9640609191333p4a15f00bt90e0e3ca240e7c99@mail.gmail.com> (raw)
In-Reply-To: <92c85b0e0609190621t52e8d65cs5e988b0fda31c2a1@mail.gmail.com>
On 9/19/06, Alon Keren <alon.keren@gmail.com> wrote:
> My aim is to have the ability to regularly build and maintain
> completely customized Linux systems.
This should be possible by using your own local portage tree (probably
based initially on Gentoo's tree) that you update somewhat manually
with ebuilds and eclasses as you want. Combined with pre-built binary
packages, and a 'golden' portage configuration and world file, it
should be relatively simple & quick to stage a new system.
If Gentoo's minimal installation CD and a stage1 install doesn't work
for you, you can build your own release media with catalyst (no, it
isn't just for rebuilding the toolchain).
This _is_ going to require a solid understanding of how Gentoo/Portage
works, but not necessarily how to write ebuilds/eclasses. You need to
understand what we mean by "portage tree", "world file", "use flags",
"profile", "binary packages", etc. The best way to acquire this
knowledge is to install and use Gentoo, daily, for something
significant (like your desktop!).
> The ROOT variable is probably a major part of the solution, but is it
> enough? I've also found '/usr/portage/scripts/bootstrap.sh', which
> seems suspiciously relevant, but comes with little external
> documentation.
bootstrap.sh _is_ for only rebuilding the toolchain. Probably not
what you want at all....
The ROOT variable is used to install packages into a different (fex
chroot) directory. It is usually used for things like
cross-compilation environments where one wants to build binary
packages for another system, although not always.
The normal way of installing a new system in a chroot from a live
system is to use the "Knoppix Installation" instructions [1].
-Richard
[1] http://www.gentoo.org/doc/en/altinstall.xml#doc_chap3
PS: list replies only please
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-19 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 13:21 [gentoo-user] Creating a LFS system with Portage Alon Keren
2006-09-19 19:54 ` Daniel da Veiga
2006-09-19 20:33 ` Richard Fish [this message]
2006-09-20 5:24 ` Alon Keren
[not found] <6WsV4-8eP-11@gated-at.bofh.it>
[not found] ` <6WutO-430-7@gated-at.bofh.it>
2006-09-19 1:06 ` Peter Wu
-- strict thread matches above, loose matches on Subject: below --
2006-09-18 15:05 Alon Keren
2006-09-18 16:16 ` Hans-Werner Hilse
2006-09-18 16:44 ` Alan McKinnon
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=7573e9640609191333p4a15f00bt90e0e3ca240e7c99@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=alon.keren@gmail.com \
--cc=gentoo-user@lists.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