Installing to Stateful

[Don Garrett]

I need to install CRX files onto the stateful partition to pre-populate a cache directory. 

In order to install the files onto stateful, my thinking is to create a new ebuild that is explicitly emerged onto stateful by build_image, and have it pull in dependencies for whatever belongs there.

This means creating a new dependency tree for files that will end up on stateful, but I expect it to be a very shallow tree. Also note that files on stateful are NOT installed by chromeos-install if they aren't added to an explicit whitelist.

Does this seem like the right approach?

It would probably be easier to have build_image just copy over files from /build/<board>/blah, but that feels more like a hack, given our build system.

--
Don

[Mike Frysinger]

in the past, we've talked about making it easier for packages to install most files to the rootfs but additionally install some to the stateful (specifically for the dev image).  seems like this is largely the same thing (except you'd want to always do it and not just dev images).

is there a specific place in the stateful you need ?  i'm guessing just dropping it into /usr/local wouldn't work.

having the packages install all into the right place and then letting build_image do the munging between partitions seems like the sanest route (rather than a magic /build/$BOARD/blah dir).

-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
 
 
 

[Don Garrett]

My current plan is to install into /mnt/stateful_partition/unencrypted/import/extensions, though that's flexible because there is a second step for my stuff to import into the encrypted stateful.

--
Don

[Don Garrett]

So, you think the ebuilds should stay as they are and build_image should just move files from rootfs to stateful?

How about anything in /mnt/stateful_partition ends up on the stateful partition in the same relative location?

--
Don

[Mike Frysinger]

right, i think the packages shouldn't need to install to a magic location and know that it'll be moved somewhere else.  have them install into the final place you want, and build_image will make sure it ends up there.

we have a new cros-constants.eclass and it sounds like this path would fit well in that so ebuilds need not use the full path to the stateful themselves.

-mike

[Don Garrett]

Well, what I was just thinking was that I should investigate if/can build_image mount stateful normally before doing the emerge. If that's done, this rest of this happens for free.

On Tue, Aug 13, 2013 at 9:39 AM, Aviv Keshet <ake...@google.com> wrote:

FYI the CL that creates the cros-constants.eclass, https://gerrit.chromium.org/gerrit/#/c/62880/, has not yet been merged (but you can go ahead and create it too if you need it).

--
Don

[Don Garrett]

Here's the CL for what I'm thinking.

https://gerrit.chromium.org/gerrit/#/c/65788/

--
Don