Re: [MirageOS-devel] [ANN] IPv6 on Mirage!

[Thomas Leonard <talex5@xxxxxxxxx>]

On 20 November 2014 14:46, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
> On 20 Nov 2014, at 07:13, Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx> wrote:
>>
>>
>> Then when you want to use foo in your project:
>>
>>     $ opam install foo-mirage
>>
>> In your "config.ml":
>>
>>     open Mirage (* to load the basic combinators *)
>>     open Foo_mirage (* to load the combinators for foo *)
>>     let main = foreign "Make" (foo @-> job)
>
> I'm not a fan of having to open Foo_mirage to use it in the configuration 
> file.  That means that you need keep track of the library dependencies when 
> writing configuration files, which the current system does a wonderful job of 
> getting rid of.
>
>>>>> - We will brainstorm in the next mirage call and in Cambridge about the 
>>>>> longer term solution of configuration modularity (which will require some 
>>>>> work to get right, and so won't happen in the very short term).  ThomasG 
>>>>> will lead this one and take the final decision since the existing 
>>>>> configuration system is his faul^H^H creation and he understands it best.
>>
>> That "wonderful" system has been build in a couple of days, under the 
>> Cambridge snow, so I have some excuses :p
>
> It's certainly a heaven send compared to the old systems we had for 
> configuring Mirage.  The bad old days of using `opam switch` for different 
> backends is why I'm fervently hoping that issues like the AMD64 redzone never 
> come in to bite us...

It would be useful to know what the problems with using a switch were.
It would make packaging the TLS stuff easier if we didn't need e.g.
separate gmp.unix/gmp.xen, ctypes.unix/ctypes.xen, etc packages, when
the only difference between them is the platform they're compiled for.

Could the mirage tool manage switches for us?


-- 
Dr Thomas Leonard        http://0install.net/
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel