Hello the list,
I have some news about OSCARonDebian: the current version allows to install a
cluster (even if I still have some minor bugs), ie I can complete steps 1 to
6.
The main difference with the "official" OSCAR is of course the difference of
binary package format (I have created a set of Debian packages and convert
other RPMs) but also some modifications to match with Debian tools. For
example, the repository is not completely local, I use an online repository
and only Debian packages included in OSCAR packages are managed through a
local repository. I will not details the part because I did not need to
really modify OSCAR for that.
For the Debian port, I try to be as close as possible to the current OSCAR
version. Nevertheless, some OSCAR scripts are currently based on RPM. To
minimize modifications, I have audited the OSCAR code and created some basic
functions to replace RPM based commands. All these functions are currently
centralized in one directory (one directory for each binary package format
and each file of this directory are compliant to a common interface).
Currently, two files has been created: Repository.pm and PkgInfo.pm.
Repository.pm provides simple functions to setup/check repository for binary
packages, and PkgInfo.pm provides simple functions to get package information
(usefull to manage prereqs packages). The advantage of this approach is to
centralize files for a specific binary package format in a single location.
The port on a new distro/binary package (Apple) is simpler.
To summarize, I currently have the following code organization:
OSCAR_source_location ---> Deb ---> Repository.pm, PkgInfo.pm
|--> RPM ---> Repository.pm, PkgInfo.pm
I also have made a modification of Makefiles to automatically install only
needed files during the execution of the "make install" command. So after the
"make install" command, we have:
/opt/oscar ---> Distro ---> Repository.pm, PkgInfo.pm
and Repository.pm, PkgInfo.pm are the specific files for the distro/binary
package format.
Then, the OSCAR code just have to include Distro::Repository.pm and/or
Distro::PkgInfo.pm and use the common interface (I do not detail the
interface here).
I have modified OSCAR scripts which were initially based on RPM to this new
approach (eg install_cluster).
Do you think it is the good approach? Do you think it is a kind of solution
which can be included in OSCAR?
If you want details or if you have questions, feel free to contact me.
Thanks,
PS: the OSCARonDebian website is not completely up-to-date, I will do my best
to update it ASAP.
PS2: the CVS repository for OSCARonDebian is online
(http://ssi-oscar.irisa.fr/oscarondebian/cvs.html)
--
Geoffroy Vall�e
SSI-OSCAR (http://ssi-oscar.irisa.fr/)
OSCARonDebian (http://ssi-oscar.irisa.fr/oscarondebian/)
-------------------------------------------------------
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
