On Apr 28, 2005, at 10:40 AM, Thomas Naughton wrote:
One other thing that just hit me as I was starting a test. We could make a
bit better use of the 'make install' stuff to get the most basic things
installed/bootstrapped.
Since, users are strongly encouraged to logout/login after the 'make install' step. We have them starting a new shell too! :)
We could get a very basic set of stuff installed at this point, and could
add necessary hooks to remove it via the 'make clean' if desired.
Something like:
- Detect distro
- Install DepMan/PackMan
- Install recommended "concrete" module for DepMan/PackMan based on distro
(which could be overriden by a configure flag,
e.g. --with-{depman,packman}-concrete)
- Switcher/Modules (not all the core-pkg modules, just Switcher/Modules)
- etc.
Basically this moves some of the bootstrap logic out of the share/prereq
area and into the configure/build/install area...might not be a great idea
since we've been beefing about issues with that lately?
Actually, not a bad idea -- why not have configure / make all / make install do some actual work?
Note: right now we're skipping "make all", but perhaps this can be added back in...?
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
