Le Mercredi 27 Avril 2005 05:57, Jeff Squyres a �crit�:
> Sounds great! Is this stuff in addition to the PackMan/DepMan stuff?
>
> More specifically, is this package-management-related stuff? That is,
> can the actions you implemented be abstractly considered part of
> PackMan? Could your interface functions become part of PackMan? Or
> are your functions different in scope/functionality than what is in
> PackMan?
>
> I ask because it would seem nice to only have to write 2 components for
> a new packaging system (i.e., PackMan/Depman) rather than 4
> (PackMan/DepMan/Repository/PkgInfo). The goal of a good component
> system (IMHO) is to be able to extend support for a new kind of system
> by writing a small number components ("plugins").
There are no technical reasons to not include my code in DepMan/PackMan, and I
am not against the idea. :-)
But to be sure that it is the good solution, the list of functions I currently
have in the two files are:
Repository.pm
* check_local_repository: check/setup of the local repository, called only in
install_cluster to remove commands for a specific binary package format
PkgInfo.pm
* which_perlQt_name: package name does not follow same rules for Deb packages
and RPM packages so we need to find the good name for perlQt (which is
prereqs packages so we do not have a mechanism like for OPKG with the
config.xml file to automatically find the name of packages).
* which_perltk_name: same thing for perl-tk
* get_pkg_dir: allows to find the directory for packages (ie Debs or RPM);
used in some scripts
* get_package_version: gets the version of a given package
* get_pkg_list_in_dir remove_pkg: gets the list of binary packages in a given
directory.
I think that most of these functions can be included in PackMan (most of the
functions are about packages) but do you think it is a good idea to include
the function check_local_repository?
>
> On Apr 26, 2005, at 2:19 PM, Geoffroy Vall�e wrote:
> > 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
--
Geoffroy Vall�e, Ph.D.
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
