From: Jeff S. <jsq...@la...> - 2005-04-27 09:58:00
|
Sounds great! Is this stuff in addition to the PackMan/DepMan stuff? More specifically, is this package-management-related stuff? That is,=20= can the actions you implemented be abstractly considered part of=20 PackMan? Could your interface functions become part of PackMan? Or=20 are your functions different in scope/functionality than what is in=20 PackMan? I ask because it would seem nice to only have to write 2 components for=20= a new packaging system (i.e., PackMan/Depman) rather than 4=20 (PackMan/DepMan/Repository/PkgInfo). The goal of a good component=20 system (IMHO) is to be able to extend support for a new kind of system=20= by writing a small number components ("plugins"). On Apr 26, 2005, at 2:19 PM, Geoffroy Vall=E9e wrote: > Hello the list, > > I have some news about OSCARonDebian: the current version allows to=20 > install a > cluster (even if I still have some minor bugs), ie I can complete=20 > steps 1 to > 6. > > The main difference with the "official" OSCAR is of course the=20 > difference of > binary package format (I have created a set of Debian packages and=20 > convert > other RPMs) but also some modifications to match with Debian tools. = For > example, the repository is not completely local, I use an online=20 > repository > and only Debian packages included in OSCAR packages are managed=20 > 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=20= > OSCAR > version. Nevertheless, some OSCAR scripts are currently based on RPM.=20= > To > minimize modifications, I have audited the OSCAR code and created some=20= > basic > functions to replace RPM based commands. All these functions are=20 > currently > centralized in one directory (one directory for each binary package=20 > 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=20= > binary > packages, and PkgInfo.pm provides simple functions to get package=20 > information > (usefull to manage prereqs packages). The advantage of this approach=20= > is to > centralize files for a specific binary package format in a single=20 > 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,=20 > PkgInfo.pm > I also have made a modification of Makefiles to automatically install=20= > only > needed files during the execution of the "make install" command. So=20 > 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=20 > 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=20 > this new > approach (eg install_cluster). > > Do you think it is the good approach? Do you think it is a kind of=20 > 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=20= > my best > to update it ASAP. > PS2: the CVS repository for OSCARonDebian is online > (http://ssi-oscar.irisa.fr/oscarondebian/cvs.html) > --=20 > Geoffroy Vall=E9e > 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?id=105hix > _______________________________________________ > Oscar-devel mailing list > Osc...@li... > https://lists.sourceforge.net/lists/listinfo/oscar-devel > --=20 {+} Jeff Squyres {+} jsq...@la... {+} http://www.lam-mpi.org/ |