Re: Bootstrapping ark on other hosts

Joel S says:

> 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.

Generally, we try to teach packages to use their *deploy*
area.

This really only breaks with (off the top of my head) Python
and Perl.  That's because when you type 'perl', it's not
really the Perl package you want, it's the perl package plus
the 45 add-on packages that you also tossed in.  We achieve
the desired effect by "revealing" all the add-ons into
/our/lib/perl (or some moral equiv), and then telling the
perl binary to look under there.

However: at boot time, we could probably get by with a
pretty plain Python (and/or Perl, if required).  Could we
multiple-deploy (including into /d/arkboot), and then force
a setting of PYTHONPATH for long enough to get the stuff
properly installed?  (I can't instantly think of a nice way
to do that...)

Or am I just barking up the wrong tree entirely?

Will


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