RE: Bootstrapping ark on other hosts

Will Partain writes:

> Joel S writes:
> 
> > The rules can be summarized by this table.
> > 
> >            boot directory              target (our) directory
> > host       @team:ark-dirs:ARK_BOOT@    @team:ark-dirs:OUR@
> > ----       ------------------------    ----------------------
> > gold       /usr/local                  /our
> > arkboot    /our                        /d/arkboot
> > other      /d/arkboot                  /our
> 
> I wonder if you could use the multiple-deploy-areas thing to
> cut out one step; giving:
> 
>   gold       /usr/local                  /our, /d/arkboot
>   other      /d/arkboot                  /our
> 
> For the boot-ish packages, just give them <file-namespaces>
> something like
> 
>    <file-namespaces><list>
>      <item>/our</item>
>      <item>/d/arkboot</item>
>    </list></file-namespaces>
> 
> plus all extra stuff in package/ALL
> (e.g. <namespace-deploy-map>), and build away on 'gold'.
> When done, you have what you want in /d/arkboot, as a
> side-effect.
> 
> (There may be issues with Python, which does *weird* things
> about trying to find where its libraries are.)
> 
> Maybe you've already found the flaw in this plan?

The problem with multiple-deploy areas is that ark configures a package only
once, typically targeting /our.  Packages looking for for libaries in
/our/lib will have trouble running from NFS mounted /d/arkboot.

Experimentation continues.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf