[gentoo-releng] short catalyst delay

[gentoo-releng] short catalyst delay

[John Davis]

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

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


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-releng] short catalyst delay

[Kumba]

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

-- 
"Such is oft the course of deeds that move the wheels of the world: 
small hands do them because they must, while the eyes of the great are 
elsewhere."  --Elrond

--
gentoo-releng@gentoo.org mailing list

Re: [gentoo-releng] short catalyst delay

[John Davis]

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

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


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-releng] short catalyst delay

[Kumba]

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

John Davis wrote:


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

Should've been more verbose.  It's the patch for bootstrap that passes 
catalyst's options to EMERGE (passing EMERGE_OPTS to bootstrap.sh).  The 
primary issue is so options like pkgcache have an effect in the middle 
of building a stage2, cause bumping into an error in the middle of a 
stage2 and restarting on slow machines is not fun :)

I attached the patch, but drobbins mentioned there was some possible 
theoretical issue where it would conflict with the fetch option to 
bootstrap, but I've looked at it and I don't necessarily see what the 
possible problem could be.  Maybe someone has an idea.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: 
small hands do them because they must, while the eyes of the great are 
elsewhere."  --Elrond

[-- Attachment #2: catalyst-bootstrapsh.patch --]
[-- Type: text/plain, Size: 554 bytes --]

--- bootstrap.sh.orig	2004-01-12 03:18:34.413518344 -0500
+++ bootstrap.sh	2004-01-12 03:18:19.176834672 -0500
@@ -67,6 +67,14 @@ then
 	echo "Fetching all bootstrap-related archives..."
 else
 	echo "Starting Bootstrap of base system ..."
+
+	# See if ${EMERGE_OPTS} exists
+	# Catalyst uses this variable, and if pkgcache is set, catalyst passes a few options
+	# to emerge to use pre-exitsing packages, but bootstrap needs to know this
+	if [ ! -z "${EMERGE_OPTS}" ]
+	then
+		STRAP_EMERGE_OPTS="${STRAP_EMERGE_OPTS} ${EMERGE_OPTS}"
+	fi
 fi
 echo
 


[-- Attachment #3: Type: text/plain, Size: 40 bytes --]

--
gentoo-releng@gentoo.org mailing list