> 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 , 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