From: "Alon Keren" <alon.keren@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Creating a LFS system with Portage
Date: Tue, 19 Sep 2006 13:21:30 +0000 [thread overview]
Message-ID: <92c85b0e0609190621t52e8d65cs5e988b0fda31c2a1@mail.gmail.com> (raw)
Alan McKinnon wrote:
> I'm not sure why you want to do this or what your line of
> reasoning is. A stage 1 gentoo install is very similar to
> building LFS, except that you don't have to type './configure
> && make && sudo make install' 300 times. Well, conceptually
> similar at least.
>
> The whole point of LFS is to do it by hand and see how it all
> works at an even lower level than gentoo provides. You could
> use portage to automate the LFS build process, but then you end
> up with essentially a clone of gentoo. I say this as someone
> who has built an LFS as a learning exercise then moved on to
> gentoo for pragmatic reasons.
>
> Perhaps if you explained why you want to try this and especially
> what you want to accomplish, then we can advise you better.
>
My aim is to have the ability to regularly build and maintain
completely customized Linux systems. I simply don't want to be
dependent - at any stage - on the whims or habits of a distribution.
While LFS allows me to build a completely customized Linux system, it
takes, as you say, a lot of time and effort to build a single one.
Also, it offers nothing in the sense of package-management.
So, what I'm looking for is something to automate the LFS
build-process and to do it under some system of package-management.
Portage seemls likely to meet those needs.
>From what I read about stage1 and stage2, they both come as is, which
is somewhat problematic for my needs (for examle, if I want to use one
version of gcc instead of another). Even if stage1 is used 'out of the
box', some mechanism should be in place in order to build a new system
on a chroot environment, no?
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.
>
> > Please CC me your replies as I'm not subscribed to messages
> > from this list
>
> Nope. Asking that is exceptionally rude. I wade through 200+
> messages per day looking for places I can assist others. The
> least you can do is subscribe to the list like everyone else
> (and how did you manage to post without a subscription?), and
> download the same looking for replies to your question.
> Besides, the answers you get might help someone else.
I'm sorry that you find my request rude. I would rather not go through
200 messages every day if I could help it, and I personally don't find
it too troublesome to add an address to the CC line. Replying to the
list and having me as CC will obviously not prevent others to take
place in the discussion or read it later on as reference.
At any case, I would look in online archives to search for any
messages which haven't reached me.
Alon
PS.
Please CC me your replies as I'm not subscribed to messages from this list
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-09-19 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 13:21 Alon Keren [this message]
2006-09-19 19:54 ` [gentoo-user] Creating a LFS system with Portage Daniel da Veiga
2006-09-19 20:33 ` Richard Fish
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=92c85b0e0609190621t52e8d65cs5e988b0fda31c2a1@mail.gmail.com \
--to=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