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

Re: [MirageOS-devel] Random thought for an OPAM feature


  • To: mirageos-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Hannes Mehnert <hannes@xxxxxxxxxxx>
  • Date: Thu, 04 Jun 2015 11:45:56 +0100
  • Delivery-date: Thu, 04 Jun 2015 10:46:23 +0000
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>
  • Openpgp: id=11B5464249B5BD858FFF6328BC896588DF7C28EE

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi,

On 06/04/2015 08:49, Thomas Gazagnaire wrote:
> Libraries in mirage-dev are in flux and people using it should
> expect breakage -- reporting these breakages on the list or on
> GitHub is *very* useful to converge to a stable state. Once
> stabilised, libraries are supposed to be properly release and
> migrate (in bulk) to opam-repository. Or we can have a
> mirage-dev-dev repository to avoid this but I would rather avoid
> this :p

I think the main source of trouble is that some repositories are not
packaged and thus it is not obvious which are their dependencies:
- - mirage-skeleton/mirage-www: should it work with
mirage-as-released-in-opam? or the development repo mirage-dev? or
master from various packages?

In my opinion we should do releases as we go, but have the master
branches of mirage-skeleton and mirage-www working with the
opam-repository releases of our toolchains.

Additionally, we should have dev branches in those repositories which
work with packages from mirage-dev.

We can easily setup travis to check those invariants (if we agree on
them) and document this somewhere (gladly it follows intuition:
potential new people will opam install mirage and then git clone
mirage-skeleton (which defaults to master), and expect this to work).


just my 2 lepton,

hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCQAGBQJVcCxkAAoJELyJZYjffCjuH/EP/jRvLKeowtCFZVmfZgpGSrtG
bGNhmZizq7YT8fHjwKGXZ1MgF91IDj9tX1cEoRzSehlR//yNkASmpMtj0TUmdne9
hgHioPI2ER2Q3NIUtRd/A4zhWDS5xyzRFdgnRK4HZ8jiSUq+jIYerIvF/RdEgliS
45E9iru1P4HRXzWvL8zhzudQS178ZBST5Bme8yG5ruDiLTGJNOIdzT7NTug0KJJA
kcfHVh+DEyobJA8vFj9kYcCFdp9tw990cPzQYa6l0UhX66pfwZx+O1eM0V7PZybn
mXsZCkz7JGCxkuVLf7fHodsIWfh7WBmvLU9kHXINk9tC5mESuSj63L1ApYny39NB
wwgYM2wBdTZaWe7XNDrXXk/USM8KYufjXVcom1vdLCsgAP9wPZ0bgcTWHLtU4xeA
wwD9o53yna7xmQe5fDyZbXtXcIf7ot2pEkIj0KcwrtfRDv7mPO+MFTTa+tEOGE3c
HVZpoplup8feP45ZocqtT/mkqLdMx43ohYhfIdEdsB/S98bXgIw2nxOSiUhob4qj
5b6jk2hfQwYcNgIwYqIMUfBfnwGuZ5lq205Mf+J4iNTQDBd40g8/X95twP4Y75/r
3rM1qrSzYHVIwp0G7dZvzQoZGGuNOgNGpCQ5auEtQWIe+84yzK+TXNJU6hmNXZSC
lI9Xl0wRE3fi8LMIOcTq
=zunQ
-----END PGP SIGNATURE-----

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


 


Rackspace

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