[MirageOS-devel] V1 vs V2 mirage-types

[Hannes Mehnert <hannes@xxxxxxxxxxx>]

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

hey,

slowly following up - I still do not understand why we would want to
have two interface versions here -- shouldn't versioning be kept at
the package level rather than the interface level.

So, mirage-2 implies that mirage-V1-types are stable. That's very
confusing (eso for new people).

Why should we ever need two versions of an interface? The current
amount of code and external users is small enough that an API change
is best done in all dependent libraries. Also, in the future, if
someone needs mirage-x she should install the appropriate mirage-types
package and dependent packages, or did I get something wrong?

I propose to rename V1.mli to mirage.mli and V1_LWT.mli to
mirage_lwt.mli. Getting rid of the interface version madness from the
beginning. Rather focus on fixing existing software (once an interface
changes) than on backwards compatibility (I'd personally delay that as
long as we can). Developers can obviously pin mirage-types (or work on
branches), and merge once all core libraries have an updated interface.

I've still to see the use case where we really want to use _old_ and
_new_ mirage APIs side by side in the same application (or the missing
piece why we would want to have multiple API versions)...


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

iQIcBAEBCQAGBQJUY5XyAAoJELyJZYjffCjuxqMP/jGaKvFiK9CbgfPa3SoljJ1d
7NNKWHdr9lXegyGF+O4nNDRNnpByXA/+GOt5SBe34LjTqNwWalyyVSoDxLcxJxv0
F//lGpwQHCqCkzn5c6lsMHyk6oAG5B8T1QuULM9nMEKLNadPK+Hk2qQF+Q6R5qJk
ZPXQaXkYcPoSkmv7/+MqIvpX1QTzmFwKndgG7E2ayo1kDCGtmKle1s9i/6FoIuoo
cqwzERq3LFjVx2ur4PR3IIkXsWiJmEKpgogZcDhLusxfSIyvr9BZgrtpYau1ymUk
CpqNQo9YqDtXvK5aPiXdjjEUPVEtX7znB+Bh88WWhbdDdgG/EhkVMkbMzxB/4oth
rB5VkY21YUPDKGymc9RAD41VC4CvUJofSZap5OaQfxlOZyPaV3OjX3IA+mibCYPE
+2gOk2Bt/nrh8BEDcm+3KFqpD+C0+VjOWqnsNR/mW5PD1UoykZoPh3Fi3Q8vmfEy
FK34LnH4Wzl4oTSqzrETVM56P+QkZb9iZ59OhwDvoQfp9S5h1Kv2HPtIYdX9N6Fo
hwYULL964BEZOBK0QFr+1KOyM0l87HmhrGHilBpM9kpHYXyoxTx7v0hDdpyaQNE7
OFTFu953MZFQcGKEBhtJ8HPYm7f50fMuy9670MRHnE6Ljrq3TXld3O5e5VV8AMGj
pMVEgfbGAR2lxfw7XYiM
=xNCV
-----END PGP SIGNATURE-----

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