OS.*

[Vincent Bernardoff <vb@xxxxxxxxxxxxxx>]

Hi,

Just a little opinion poll who really likes having mirage-platform 
modules packed under OS.* ? Personally it makes the packaging of my 
library more complicated (because for example, xenctrl have a Eventchn 
module, whereas in Mirage it is OS.Eventchn, so I can't just use 
Eventchn in my library and be able to recompile between backends without 
code changes) and I don't like very much the packing feature overall.
If pack is going to be used for Mirage, do anybody see a not too 
annoying or ugly solution to my problem ?
A solution could be to functorize my library over all Xen-things that it 
uses. But it would imply that we write the signature of all Xen related 
packages explicitely (module type S = sig end). That would certainly work.
The drawback of this approach is that it makes my library a functor, 
which needs to be instanciated, and so on.
Removing the OS.* thing would make it work out of the box.


Dave pointed out that the mirage-unix package exports a OS.* namespace 
as well. But certainly, the UNIX version of Xen libs would not exist 
behind OS would they ?

Cheers,

Vincent