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

[MirageOS-devel] deprecating older mirage packages

  • To: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Wed, 9 Aug 2017 14:23:06 +0100
  • Delivery-date: Wed, 09 Aug 2017 13:23:24 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:to; q=dns; s=selector1; b=gZWxqMoL63RZFAXtDz3HQ +hw9jUR3dnCRwCJb335MZNE1qbqq45+SPDbL8brzx1+eNPmUAb8jUCW1In3s5pXH +qTqQuFjf4Y1Na/88HIlHGzHGo5S0TX7zISBZreJG+R4CkB6xTiCV7U+mhEiZw4V eqQJWwRHpqsYat09OMZJF4=
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

Dear all,

I've been wondering for a while how to deprecate some of the older mirage 
packages from appearing in typical opam searches for (e.g.) the "org:mirage" 
tag.  Right now, you get packages like mirari appearing in that.

The reason for this is that we don't really distinguish between versions of our 
platform as we tag things with org:mirage.

We could

- add a messages: field to a package to indicate that it's part of mirage1/2 
and therefore probably not what the user actually wants.
- add a new mirage3 tag to indicate it's specifically compatible with mirage3
- do some fancy dependency analysis to figure out if mirage-types-lwt>3 is 
- add a boilerplate "deprecated" notice to the description files, and point 
people at the new packages.

Any other ideas/thoughts on how to drive users away from very old packages?

MirageOS-devel mailing list



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