On Thu, 2004-04-01 at 12:23, Kumba wrote:
> John Davis wrote:
> 
> > Hi all -
> > I am going to delay catalyst 1.0.5 until later tonite (or early tomorrow
> > morning) due to a bug in the default-runscript.sh that is the root of
> > the modules-update problems. If you remember, there are a lot of errors
> > about modules.conf not being created, etc.
> > 
> > Beejay is working hard on a patch for this and says that he is close. I
> > will keep you all informed.
> > 
> > Cheers,
> > //zhen
> 
> Just thought I'd fire this off as a shot, but when catalyst builds 
> stages, it autogenerates a make.conf in the stage that is rather sparse. 
>   Any thought on having it copy over an existing portage copy of 
> make.conf for the applied arch?
> 
> btw, that patch to bootstrap from months ago, that ever get put into 
> bootstrap.sh?  I know there was some theoretical conditional that 
> drobbins said could pop up, but I never figured it out.
> 
> 
> --Kumba

Kumba -
Yeah, that make.conf is created on purpose. A more verbose
make.conf.example is installed by Portage though. It mimics the old
style make.conf that has comments all over. The verbosity still exists,
just in another file.

Which patch? The emerge_opts patch so that the user can add emerge flags
such as 'pv'? The patch is not part of catalyst, so I can apply it
anytime. I would like to apply it, but I have not heard any feedback ...

Cheers,
//zhen

-- 
John Davis
Gentoo Linux Developer
<http://dev.gentoo.org/~zhen>

----
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc>
Fingerprint: 2364 71BD 4BC2 705D F338  FF70 6650 1235 1946 2D47