From: Thomas Naughton on Thursday, April 28, 2005 7:40 AM
>
>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! :)
Wow! I missed that memo!
>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.
>
I've always thought the "make install" bit was less than optimal.
Unpacking the tarball directly into /opt/oscar should really be
sufficient considering what's actually done.
I'd also like to see the "./install_cluster" only needed the first time.
That could be done explicitly via your new "make install" (or
"./configure"?) or implicitly via "oscar_wizard" (which, given our
usage, should just be "oscar").
So, I think we're agreeing that we should work on the overall
installation and startup process.
--
David N. Lombard
My comments represent my opinions, not those of Intel Corporation.
-------------------------------------------------------
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?id5hix
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
