[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] [opam-devel] opam 1.1.1 and aspcud 1.9

> On 11 Dec 2014, at 01:41, Louis Gesbert <louis.gesbert@xxxxxxxxxxxx> wrote:
> Opam build got broken between 1.1.1-1 (trusty) and 1.1.1-1build3 (utopic) 
> because the dose version was upgraded from 3.1.3-7build1 to 3.2.2-2build1. 
> It's very painful when everything types and compiles after an upgrade, but 
> gets subtly broken :(

It is indeed 'funny' the feeling of betrayal which a fully-typing yet broken 
functional program gives :)

However, rather than introducing version constraints, wouldn't it be better to 
introduce a mandatory test step to the build process (one which could possibly 
be disabled when developing opam, but would definitely be enabled when it's 
being packaged or compiled by users)? Just a minimal program which fails with 
if Dose isn't behaving as expected (using this bug as the first test case)


MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.