[gentoo-catalyst] ship /usr/portage with stage4

[gentoo-catalyst] ship /usr/portage with stage4

[Burak Arslan]

Hi there,

I've set up my first stage4 catalyst job and everything seems to be in 
order.

My final gripe with it is that I couldn't get it to ship the contents of 
/usr/portage inside the stage4 tarball. Having looked at the source, I 
guess that's because the latest portage snapshot is mount --bind'ed to 
the chroot environment, which is unmounted before creating the tarball.

Any suggestions? Am I missing something obvious here?

Best regards,
Burak

ps: I wouldn't prefer to ship the archive and add this to local.start:

if [ -f /portage-latest.tar.bz2 ]; then tar xjpf /portage-latest.tar.bz2 
-C /usr && rm /portage-latest.tar.bz2; fi

Re: [gentoo-catalyst] ship /usr/portage with stage4

[Chris White]

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

On Wed, Feb 20, 2013 at 8:51 AM, Burak Arslan <burak.arslan@arskom.com.tr>wrote:

> Hi there,
>
> I've set up my first stage4 catalyst job and everything seems to be in
> order.
>
> My final gripe with it is that I couldn't get it to ship the contents of
> /usr/portage inside the stage4 tarball. Having looked at the source, I
> guess that's because the latest portage snapshot is mount --bind'ed to the
> chroot environment, which is unmounted before creating the tarball.
>
> Any suggestions? Am I missing something obvious here?
>

Yes, you need to disable snapcache in your catalyst config `options` value:

# snapcache = cache the snapshot so that it can be bind-mounted into the
chroot.
# WARNING: moving parts of the portage tree from within fsscript *will*
break
# your cache. The cache is unlinked before any empty or rm processing,
though.
#

In general I tend to keep a different catalyst config for stage 4 and stage
1-3, passing in the appropriate config file using `-c`

- Chris

[-- Attachment #2: Type: text/html, Size: 1855 bytes --]