I just committed a bunch of changes to Package.pm and wizard_prep that
allow packages to live either in $OSCAR_HOME/packages or
/var/lib/oscar/packages. This is the first step towards getting rid of
the ugliness that is $OSCAR_HOME. :-)
Known limitations:
- doesn't properly handle if the same package name is in both locations
(this problem will solve itself when we go to just one location)
- test_cluster script hasn't been updated yet (it still only looks in
$OSCAR_HOME); will be done soon
This also necessitated updating a bunch of scripts in various packages to
use a new environment variable named $OSCAR_PACKAGE_HOME instead of
$OSCAR_HOME. So OSCAR_PACKAGE_HOME is set before OSCAR invokes any API
call, and points to the top-level directory of that package. For example,
$OSCAR_PACKAGE_HOME/scripts points to that package's scripts directory.
This is because a package may not be located under $OSCAR_HOME anymore.
It all seems to work. Let me know if anyone finds any problems.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
