I think this stuff has great promise, and is the Right Way to go for OSCAR.
A few comments below...
On Apr 27, 2005, at 11:46 AM, Geoffroy Vall�e wrote:
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
I'm not quite sure I understand this -- can you explain more?
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
Hmm. I'm wary of these 2 which_*_names functions for a generalized interface. What exactly is the problem here? I'm not quite sure I understand your explanation...
* get_pkg_dir: allows to find the directory for packages (ie Debs or RPM);
used in some scripts
Ah -- so this would return a tuple of dirs, e.g., ("RPMS", "SRPMS")?
* 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.
Is remove_pkg related to this? I'm not quite sure why it's listed here...?
--
{+} 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?id5hix _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
