So the option I recommend would be to use the minimal image created by the creation of an "empty" SIS image (i.e. : without providing any RPM).
The oscarsample/*.rpmlist should be completely discarded and the rpmlist should be provided by the chrooted (in the minimal image) update-rpm should be used.
This might not be a bad thing.
But we'd still need *some* RPM list, right? Something for that base/minimal set of RPMs to establish all the required dependencies for that distro, right?
Also, is there a reason we're still using oscarsample/*.rpmlist instead of packages/base/config.xml? I notice that the server RPMs are in base/config.xml, but the client RPMs are still in oscarsample/*.rpmlist.
Was there a technical reason for that, or just hysterical raisins?
It maybe interesting, then, to create a "virtual" RPM for OSCAR that would simply contain PreReqs (for instance an X windowing system, etc.).
This virtual RPM will be distro and version dependant but can be automatically generated from the information contain in the config.xml that is directly avalaible in ODA.
-- {+} 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
