From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] initial compile time
Date: Mon, 28 Aug 2017 09:47:23 -0700 [thread overview]
Message-ID: <CAGfcS_=thDH+K_RYU1XeGjvqk3dKuQhAyeWnLbvONNt5RyuggA@mail.gmail.com> (raw)
In-Reply-To: <2f97694a-54e0-879c-3a0f-c6cdf41939cd@gmail.com>
On Mon, Aug 28, 2017 at 9:08 AM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 28/08/2017 13:41, mad.scientist.at.large@tutanota.com wrote:
>> Ok, i'm starting to understand the install instructions, a steeper curve
>> than i expected but still way easier than LFS.
>> So, on a dual core athlon II 6000 (two cores, 3ghz) roughly how long
>> will stage3 take to compile, roughly?
>
> How many extra USE flags did you set? What software did you decide to
> add? How old is the stage 3 you used? A recent one will obviously need
> fewer recompiles than a 6-month old one. But to portage it's all the
> same - make a list of stuff to be done and do it from the beginning.
>
I imagine that some people like to rebuild everything after changing
their CFLAGS, but there is certainly no requirement to do so.
Also, I tend to favor getting the system booting on its own before
fiddling with it. There isn't much you need to build before you have
the system booting, and at that point you're at least running while
you're doing the rest. If I'm going to switch the init implementation
then I'll do that before the first boot since that impacts the grub
configuration. Systemd does take a bit to build, but it is still a
far cry from doing a ton of rebuilds.
However, if you do have a /etc/portage configuration you like, and a
/var/lib/portage/world, then you can just update these and the profile
and just do an emerge -NDu world and watch it all come into place. I
have a typical set of configuration files I deploy on any new system
so I will often build this stuff directly before rebooting (which
includes stuff like systemd, vim, screen, grub, dracut, and so on).
--
Rich
next prev parent reply other threads:[~2017-08-28 16:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 11:41 [gentoo-user] initial compile time mad.scientist.at.large
2017-08-28 16:08 ` Alan McKinnon
2017-08-28 16:47 ` Rich Freeman [this message]
2017-08-28 16:48 ` Alan McKinnon
2017-08-28 18:37 ` allan gottlieb
2017-08-28 18:45 ` J. Roeleveld
2017-08-28 20:34 ` mad.scientist.at.large
2017-08-28 18:55 ` Rich Freeman
2017-08-28 20:31 ` mad.scientist.at.large
2017-08-29 0:18 ` allan gottlieb
2017-08-28 20:20 ` mad.scientist.at.large
2017-08-29 5:50 ` J García
2017-08-29 11:17 ` Rich Freeman
2017-08-29 11:08 ` Alan McKinnon
2017-08-29 16:47 ` Mick
2017-08-29 19:30 ` Dale
2017-08-30 22:05 ` Alan McKinnon
2017-08-30 22:03 ` Alan McKinnon
2017-08-28 16:55 ` John Blinka
2017-08-28 20:09 ` Alan McKinnon
2017-08-28 20:25 ` mad.scientist.at.large
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='CAGfcS_=thDH+K_RYU1XeGjvqk3dKuQhAyeWnLbvONNt5RyuggA@mail.gmail.com' \
--to=rich0@gentoo.org \
--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