Re: [PATCH 0/2] Populate site config files content to rootfs

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2011-08-11 at 22:31 +0800, Lianhao Lu wrote:
> This series of patches fixed the bug #892. Currently, the site config 
> files used in the cross compiling environment generated by meta-toolchain 
> partly come from SITECONFIG_SYSROOT_CACHE, where each package will put 
> their own site config cache file during their populate-sysroot task.
> 
> However, there is no way to guarantee the meta-toolchain to collect these 
> site config cache files after all other packages have finished their 
> populate-sysroot tasks. Since we now encourage users to use the same rootfs 
> for both running and cross-compiling, by populating the site config files'
> content into rootfs and having the CONFIG_SITE pointing to the rootfs, we 
> can gurantee the cross compiling environment not missing any site config 
> cache files' content.

I'm afraid I'm not very keen on this patch since it complicates the
situation and I'm not sure its an improvement. We strive very hard never
to add files to a rootfs which aren't packaged and this approach breaks
that (and always adds them to certain image types which again, I worry
about).

Can't we use the no_cache option to siteinfo_get_files() to address this
bug, yet leave the cache files where they are currently located as part
of the toolchain?

Ultimately we could specific extra cache files to add (such as eglibc)
and ensure we have the correct dependencies to ensure the caches are
generated.

Cheers,

Richard