Not checking for installed RPMs would be fairly simple to implement.
However, that's not the way it's done in real life -- there you have a seed set of RPMs the form a minimal core to allow rpm(1) to do it's job. We clearly have those things available to us as the image build process does that now. This is a better approach, as we're closer to actual practice, rather than trying to invent some other mechanism.
Could be sticky, though -- that's currently part of the black-box SIS "create image" stuff. So AFAIK, from DM's perspective (and therefore update-rpm's perspective), there's no image and no empty RPM base to examine before we invoke SIS's "create image" functionality.
I'll also take a look at ignoring the installed base, if that's truly as simple a fix as I think it is, then I'll do that too, so we can at least try it out -- better to pick from two alternatives than one.
This might be easiest / best.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
