From: Matthias Langer <mlangc@gmx.at>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: default stage3 (was : [gentoo-user] Is Gentoo still on the right path?)
Date: Mon, 21 Nov 2005 14:09:45 +0100 [thread overview]
Message-ID: <1132578585.10357.20.camel@sputnik886.ruz-net> (raw)
In-Reply-To: <1132577851.10357.12.camel@sputnik886.ruz-net>
On Mon, 2005-11-21 at 13:57 +0100, Matthias Langer wrote:
> On Mon, 2005-11-21 at 21:33 +0900, Steve B wrote:
> > WTF.. I'm getting ready to rebuild my gentoo box. I have always did a
> > stage 1 install. i was under the impression that if u used a stage 3
> > u couldn't muck with your CFLAGS or what not.
The only flag you should not change after a stage 3 install is CHOST. If
you downloaded the right stage3 tarball there is no reason to do so
unless you are cross-compiling. Note that stage1 is still available, but
no longer supported by the handbook, as there is allmost no reason, even
for an experienced gentoo-er not to use stage3.
> If I'm forced to use
> > canned binaries I might as well go with FC or Debian.. I've never
> > listened to the "Gentoo is dead" comments.. but now who knows.. this
> > is just crazy.. who came up with this stupid idea? from the sounds of
> > it certianly not the Gentoo Community!
> >
>
> I think you haven't really read the discussions about this topic. As
> long as you don't edit bootstrap.sh,
>
> stage3->emerge sync->adapt make.conf, package.* files etc.->emerge -e
> world
>
> will just have the same effect as a stage1 install but
>
> - faster
> - with fewer pitfalls
>
> Regards,
> Matthias
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-21 13:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 12:33 default stage3 (was : [gentoo-user] Is Gentoo still on the right path?) Steve B
2005-11-21 12:57 ` Matthias Langer
2005-11-21 13:09 ` Matthias Langer [this message]
2005-11-21 12:57 ` Neil Bothwick
2005-11-21 13:13 ` Hemmann, Volker Armin
2005-11-21 15:17 ` Holly Bostick
2005-11-21 18:19 ` Daniel da Veiga
2005-11-21 22:33 ` Holly Bostick
2005-11-21 23:36 ` Anthony Roy
2005-11-22 7:49 ` Philip Webb
2005-11-22 9:24 ` Neil Bothwick
2005-11-22 11:22 ` Robin
2005-11-22 14:07 ` Daniel da Veiga
2005-11-22 17:24 ` Manuel McLure
2005-11-22 23:19 ` William Kenworthy
2005-11-23 0:11 ` Manuel McLure
2005-11-22 23:34 ` Neil Bothwick
2005-11-22 0:09 ` George Garvey
2005-11-22 0:17 ` Manuel McLure
2005-11-22 0:40 ` Holly Bostick
2005-11-22 2:06 ` W.Kenworthy
2005-11-22 11:32 ` Neil Bothwick
2005-11-21 19:20 ` kashani
2005-11-21 20:39 ` John J. Foster
2005-11-21 20:47 ` Jason Dodson
2005-11-21 21:38 ` kashani
2005-11-21 22:10 ` Steven Susbauer
2005-11-21 22:27 ` Manuel McLure
2005-11-22 18:26 ` Hemmann, Volker Armin
2005-11-22 18:44 ` Nagatoro
2005-11-22 20:34 ` Daniel da Veiga
2005-11-22 19:52 ` Billy Holmes
2005-11-22 21:44 ` kashani
2005-11-21 20:15 ` [gentoo-user] Re: default stage3 Allan Gottlieb
2005-11-21 20:50 ` Bob Young
2005-11-21 22:01 ` Ryan Sims
2005-11-21 23:28 ` Matthias Langer
2005-11-22 9:17 ` Neil Bothwick
2005-11-22 17:03 ` Richard Fish
2005-11-22 18:03 ` Matthias Langer
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=1132578585.10357.20.camel@sputnik886.ruz-net \
--to=mlangc@gmx.at \
--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