New host challenges: libraries

When bootstrapping Arusha onto a new host, ark will start using the newly
installed packages immediately. This results in failure when a dependent
library has not been installed.

For example, when openssh-config ran ssh-keygen on a new host, it couldn't
find libcrypto.  Why not?  This worked fine on the gold server!  The
appropriate constraints are specified in Verilab's openssh--3.7.1p2: the
<configure> method depends on deployment of zlib, openssl, and tcpwrappers.

The problem is that the <configure> method runs only on the gold host. It is
not rerun for each new host, so the constraints are ignored. I added the
same three constraints to the <deploy> method as a workaround.

A similar problem occurs after ark installs Python on a new host, but hasn't
yet installed gcc libraries. Again, their are constraints on the <configure>
method, but not on the <deploy> method.

Although repeating the constraints in <configure> and <deploy> appears to
work, it seems awkward. Shouldn't there be a way to specify these
constraints only once?

--

Joel Shprentz
National Imagery and Mapping Agency
Mailstop N-17
Washington Navy Yard, Building 213
1200 First Street, SE
Washington, DC 20303-0001

202-685-3534




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php