On Tue, 2005-05-10 at 14:34 -0400, Paul Smith wrote:
> Right now I'm working on getting some other packages installed into the
> livecd. The problem I'm having is that there doesn't seem to be any
> fully usable "test environment" that reflects the livecd I can use for
> development. What I'm looking for is something that has the contents of
> the livecd, but that also has the Portage database and tools installed
> so that I can work with emerge, ebuild, etc. and get new packages
> installed and working the way I want them to.
You could just copy the portage tree into your livecd-stage1 directory.
> I can see the livecd-stage1, for example, leaves behind an image that I
> could chroot to, but it's missing all the portage info so I can't really
> do much in terms of testing there.
Do what catalyst does. Bind mount it.
> How do you all develop and test live CDs? Is there some trick to
> getting a test image available? Or, do you do development via another
> method and only start using catalyst when everything pretty much works?
Honestly, I've been doing catalyst development (and use) long enough
that I pretty much know what to expect. When something doesn't work, I
rebuild the entire image each time. The reason for this is simple. I
do not want to do *any* manual steps outside of catalyst, since it'll do
nothing but give you trouble in the long run.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
signature.asc
Description: This is a digitally signed message part
|
