public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Felipe Ghellar <fghellar2@yahoo.com.br>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ACCEPT_KEYWORDS + bootstrap.sh
Date: Sun, 16 Mar 2003 16:33:27 -0300	[thread overview]
Message-ID: <3E74D187.2@yahoo.com.br> (raw)
In-Reply-To: <20030316190853.GA28936@cerberus.oppresses.us>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii; format=flowed, Size: 1498 bytes --]

> It doesn't ignore what the user wants. It just doesn't look where you 
> think it should.

I don't see the difference...


> If someone really wants to use newer packages to bootstrap, they can 
> edit the packages file in their profile. Otherwise things can 
> potentially break and we get more bug reports.

Of course things can break. Even "stable" packages break sometimes. And 
of course there will be bug reports. Ain't that an important (and 
desired) part of the Gentoo development process? To know what does and 
what does not work together? And find out the reason when they don't?


> if you want 
> to tune your settings for bootstrap, do it in places other than 
> make.conf and don't file bug reports if something breaks in the process.
> 
> Users can do anything they want in make.conf after bootstapping.

In <http://www.gentoo.org/doc/en/gentoo-x86-install.xml>, step 11 is 
where I set up my make.conf, and step 12 is where bootstraping takes 
place. I see no reason for step 12 to ignore what was set up in step 11.


Also, please read comment #3 in the bug report I cited earlier:
http://bugs.gentoo.org/show_bug.cgi?id=11374#c3
It contains many of the reasons why I believe make.conf should _never_ 
be ignored.


Felipe Ghellar

-- 


_______________________________________________________________________
Busca Yahoo!
O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra.
http://br.busca.yahoo.com/

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-03-16 19:29 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 [this message]
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
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=3E74D187.2@yahoo.com.br \
    --to=fghellar2@yahoo.com.br \
    --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