public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nicholas Hockey <tilt@bluecherry.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ACCEPT_KEYWORDS + bootstrap.sh
Date: 16 Mar 2003 15:00:49 -0500	[thread overview]
Message-ID: <1047844849.7420.22.camel@blackhole> (raw)
In-Reply-To: <3E74D537.7020606@yahoo.com.br>

[-- Attachment #1: Type: text/plain, Size: 1942 bytes --]

if your by a river in florida chances yer in a swamp, or near a sink
hole, not a good place to lay the foundation of your house

On Sun, 2003-03-16 at 14:49, Felipe Ghellar wrote:

> Nicholas Hockey wrote:
> > well there is a reason that the base system is set up a certain way, 
> > it's so that when you do run the bootstrap it will compile, in Linux 
> > there is no real "base system" as there is in freebsd, so the only 
> > logical way around this is to build a good foundation, which is well 
> > known to build a complete system, at the sacrifice of time.
> 
> Ok, let's simulate the installation process...
> 
> 1) I preapare everything according to the Install Guide
> 2) I set up my make.conf the way I want it, with ~x86
> 3) I run bootstrap.sh; it ignores my "unstable" choice and builds a 
> "stable" base system
> 4) I run emerge system and then complete the installation
> 5) later, I run emerge --sync and emerge -u --deep system; it now 
> follows my "unstable" choice and brings in all those packages 
> bootstrap.sh ignored
> 
> The net result is just that "sacrifice of time" you mentioned...
> 
> 
> > or they could do it your way, by the way i have some cheap land in 
> > Florida, right next to the river, i'll sell it to you, by your standards 
> > it should be a great place to build a house
> > 
> > (sorry if this sounds rude i just thought this would be a good comparison)
> 
> Sorry, I don't get your point... (and I did't take it as rude)
> 
> Felipe Ghellar

-- 
Nicholas Hockey (Tilt) <tilt@bluecherry.net>
Unix Administrator
Encrypted E-Mail is preferred..
-------------------------------------------------------------------- 
GnuPG KeyID 4EDE2B84
Key fingerprint = B916 6032 BE3D 490D 2A08  F1BC 948A A4C1 4EDE 2B84
HKP: gpg --keyserver pgp.mit.edu --recv-keys 4EDE2B84
LDAP: gpg --keyserver ldap://keyserver.pgp.com --recv-keys 4EDE2B84
--------------------------------------------------------------------

[-- Attachment #2: Type: text/html, Size: 2402 bytes --]

  reply	other threads:[~2003-03-16 20:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-16  9:22 [gentoo-dev] ACCEPT_KEYWORDS + bootstrap.sh Per Wigren
2003-03-16  9:36 ` Nicholas Hockey
2003-03-16 16:16 ` Jon Portnoy
2003-03-16 19:03   ` Felipe Ghellar
2003-03-16 19:08     ` Jon Portnoy
2003-03-16 19:33       ` Felipe Ghellar
2003-03-16 19:43       ` George Shapovalov
2003-03-16 19:23     ` Nicholas Hockey
2003-03-16 19:49       ` Felipe Ghellar
2003-03-16 20:00         ` Nicholas Hockey [this message]
2003-03-17 16:12           ` Robert Cole
2003-03-16 20:14         ` George Shapovalov
2003-03-16 20:38           ` Felipe Ghellar

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=1047844849.7420.22.camel@blackhole \
    --to=tilt@bluecherry.net \
    --cc=gentoo-dev@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