Hello Bernard,
Alternatively, you can build a SRPM including the diffs etc. (and requiring the "kernel" and probably "kernel-devel" package) so that the user can on the fly rebuild the dipc RPM based on their kernel. It would probably be a good idea to ship one that is known to work though.
Yes this is possible.
Anyways, we need to address the bigger issue here, which is how we want to treat packages that depend on specific kernels - eg. lustre, kerrighed, dipc.
Maybe one can distribute all the needed kernels, pre-patched, in an OSCAR package. This way there will be a 2.6.x kernel patched for Kerrighed, and a 2.6.x kernel patched for DIPC, etc, eventhough actually patching a kernel is rather simple (can be further simplified using a small script).
The main problem in installing such systems is figuring out what to do where. Which files to copy? Which config files to edit? What to write in them? What kernel version to patch? etc.
One can create an OSCAR Linux distribution with some of these steps taken: All the executables, documents, and config files are at the right place. One can also patch and (optionally) compile Linux kernels with each package (it seems most of them are not compatible and so can't exist together in the kernel) and set up a lilo or grub boot menu. What the user has to do now is to set the appropriate entries in the config files, and select (and compile, if needed) a kernel.
-Kamran ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
