Thanks Geoffroy. I've been looking at Kerrighed's packaging, and it seems
that creating an RPM is not suitable for systems like DIPC and Kerrighed.
The reason is that installing such systems requires patching the kernel. I
see the following problems:
1) Including a pre-compiled kernel forces others to use a specific version
of the kernel, with whatever options that were selected at the compile time.
When distributing a patch, chances are users can apply it to a similar
kernel. DIPC's kernel patch in particular is fairly small and
non-intrusive, so chances are it can be applied to other kernel versions.
2) DIPC can work on non-x86 CPUs, so distributing an i386 RPM is
restrictive.
Yes, for a user-level system, an RPM distribution is excellent. I won't
speak for Kerrighed, but creating an RPM for DIPC seems to complicates
things more than it helps.
Maybe I need to be educated on the merits of creating an RPM for a system
like DIPC
-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