[gentoo-catalyst] Pre- and post- kmerge mismatch in generic-stage-target.py

[John Howard]

Greetings,

I have been reading through the Catalyst scripts in an effort to  
understand how to build a liveCD,  and have come across something  
suspicious.  The code in generic-stage-target.py:

							# execute the script that cleans up the kernel build environment
							cmd("/bin/bash "+self.settings["controller_file"]+" post- 
kmerge ",\
								"Runscript post-kmerge failed",env=self.env)

appears to fall within the "for kname in mynames:" loop, but the  
corresponding pre-kmerge step is outside of that loop.  This wouldn't  
cause problems in when only one kernel is being built, but might  
cause problems with more than one.  Or I might be wrong in thinking  
that the pre- and post-kmerge steps should match up; if so please  
enlighten me.

Hope this is useful,
John Howard

-- 
gentoo-catalyst@g.o mailing list