On Wed, 27 Apr 2005, Geoffroy [iso-8859-1] Vall�e wrote:
Is remove_pkg related to this? I'm not quite sure why it's listed here...?
The current code (the install_cluster script) includes some commands like "rpm -e <packagename> and I don't want to break everything, so a first solution may be to use a remove_pkg function which deals with differences between RPM/Deb/.... But I am pretty sure that his kind of function can be integrated to PackMan. I think the most important is to decide what we can put in PackMan/DepMan to make the OSCAR code less specific to RPM packages.
I think this answer is clear enough and feel free to contact me if it is not.
Couple comments: I believe there is also a "chicken-and-egg" problem with some of these "distribution agnostic pkg-mgmt-system" helper routines that may be necessary just to get PackMan/DepMan installed (possibly a few other prereqs).
So, it might make since to have a bootstrap area that does the most base setup to get DepMan/PackMan tools setup.
I also see that there are some issues with naming differences among distributions. This bootstrap area could do the appropriate lookups to get prereq names (and ordering).
my $0.02, --tjn
_________________________________________________________________________ Thomas Naughton [EMAIL PROTECTED] Research Associate (865) 576-4184
