there should be a way to include a portage tree with stage4 tarballs. ideally the same tree that the stage was built with.
Arent stage 4 tarballs an unsupported 3rd party backup stage? I'm pretty sure they are... as the thread is in the Unsupported Software section of the forums. Go post that there please and mark this as INVALID. Thanks
Umm... no. The stage4 target is a *real* catalyst target that was added with catalyst2. It isn't *our* fault that a bunch of users created their *own* "stage4" (that isn't) and are confusing the situation. Rajiv: I honestly do not want this option, as it changes the definition of a stage4 tarball. All Gentoo stages have no portage tree. I would rather keep it this way, than confuse the situation by making stage4 different.
You can always stick the portage snapshot in the filesystem overlay (assuming this exists for stage4) and then extract it to /usr in your fsscript.
No, you can't. The portage tree is bind mounted if you have options=snapcache, otherwise it is extracted/deleted by catalyst automatically, which is done after the fsscript is run.
Since this really cannot be done sanely within catalyst without an enormous amount of work, I'm marking this as WONTFIX. The only decent solution that I see right now is to run something like this: #!/bin/bash VERSION=$(awk -F: '/version_stamp/{printf $2}' stage4.spec) SUBARCH=$(awk -F: '/subarch/{printf $2}' stage4.spec) catalyst2 -f stage4.spec mkdir -p /tmp/cattemp cd /tmp/cattmp tar xpf /var/tmp/catalyst2/builds/default/stage4-$SUBARCH-$VERSION.tar.bz2 tar xpf /var/tmp/catalyst2/snapshots/portage-$VERSION.tar.bz2 -C usr tar cjf ../stage4-portage-$SUBARCH-$VERSION.tar.bz2 . Sure, you'll need to fix it up for your environment (and check it for sanity) but you get the idea.