Great! For the rest of the list, it looks like mirage-dev is working with the external OPAM solver (aspcud, on Ubuntu-trusty), but not with the internal one (CentOS builds):
This is probably due to our excessive use of depopts; I will replace those with explicit virtual packages (e.g. dns-mirage) that encode all the dependencies they need.
More mysteriously, the `set -e` in the shell script isn't causing it to terminate early, so the `MIRAGE WORKS` string is always printed. We need a is-mirage-working-working script to fix our is-mirage-working script :-)
-anil
On 20 Oct 2014, at 15:09, Luke Dunstan <lukedunstan81@xxxxxxxxx> wrote:
Thanks, I was able to compile and run mirage-www on a Docker image with 4.01.
Luke
_______________________________________________ MirageOS-devel mailing list MirageOS-devel@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|