I'm not following.
Ok, I'm gonna try and explain everything better (->long email :S). I'm
having this problem with the emerge step on the livecd stage1 target.
The thing is, it tries to emerge lots of packages and due to problems with
portage mostly, it results in a interrupted build. From there I can resume
catalyst, but unfortunately it won't allow me to go back and unmerge/rebuild
packages. It also doesn't allow me to -quickly- try new emerge setups like
doing emerge --pretend on some packages (with new use flags), see what's
pulling what and how.
The only options I have is to either go on and emerge more, or do it all
over again after changing the spec. From what is written on the website,
using something like tinderbox to build a livecd would be helpful, but from
what I read you can only use it for testing, not to use in a livecd stage2.
The ideal would be to have total control of the emerge step therefore easily
avoiding circular dependencies, emerge blocks of packages at a time, easily
find and remove unnecessary packages, etc. Well, at least as easy as in our
system.
I conclude from
It does take Release Engineering upwards of a month to stabilize any
given snapshot to build a release. Maybe there's a reason for that. ;]
this is a problem for everyone, so there is no current way to go around it
is there? (actual question, not rhetoric :P)
Wouldn't it be great if you could just get in and do this small step
yourself as an option? One could always do this only to obtain a bunch of
built packages and -then- do a clean build right?
So my question is, how do you build the release cd's? You do try and error
on ebuilds like I do, and write portage overlays? Would it be bad if you
could enter the cd and manually emerge stuff yourself, solving problems at
the moment instead of building all over again everytime portage complains?
Is there a problem with the current catalyst implementation that would make
this hard to code?
Making it "easy", and thereby encouraging people, to poke around in the
caches is the absolute last thing I want to do.
Ok instead of calling it --chroot, call it --pretend. Everything a user did
would be erased. No problems with touching the ccas (it forces a clean
build) and one could still build pkg's and "play" with emerge.
Phew :). I understand you must be full of work with the new release, reply
anytime, and thanks for the help.
Cheers
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
--
[EMAIL PROTECTED] mailing list
