From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 5102181799 for ; Wed, 24 Jul 2013 18:25:41 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of thomas.gazagnaire@gmail.com) identity=pra; client-ip=209.85.212.171; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="thomas.gazagnaire@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of thomas.gazagnaire@gmail.com designates 209.85.212.171 as permitted sender) identity=mailfrom; client-ip=209.85.212.171; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="thomas.gazagnaire@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wi0-f171.google.com) identity=helo; client-ip=209.85.212.171; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="thomas.gazagnaire@gmail.com"; x-sender="postmaster@mail-wi0-f171.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArUBADX/71HRVdSrjWdsb2JhbABagzsBvluBFhYOAQEBAQcLCwkSBiSCJAEBBAE6BgE4AQMBCwEFBUY0AQUBHAYuh2MDCQYECJs8j06EcScNiFgBAQQMjz6DTG4DngKJRT+BXYJf X-IPAS-Result: ArUBADX/71HRVdSrjWdsb2JhbABagzsBvluBFhYOAQEBAQcLCwkSBiSCJAEBBAE6BgE4AQMBCwEFBUY0AQUBHAYuh2MDCQYECJs8j06EcScNiFgBAQQMjz6DTG4DngKJRT+BXYJf X-IronPort-AV: E=Sophos;i="4.89,736,1367964000"; d="scan'208";a="27189262" Received: from mail-wi0-f171.google.com ([209.85.212.171]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 24 Jul 2013 18:25:40 +0200 Received: by mail-wi0-f171.google.com with SMTP id hj3so4510452wib.16 for ; Wed, 24 Jul 2013 09:25:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=cfJKEsry1KI90en4vgCuhgmtbTNiVZ0XjtqaDlHPVIc=; b=i/BLVyBw2DoXUbSf+OWH0VDcrGpA0bj4/CkhV984xtGC4sOrwuXi0GB4MRHpCunnKV RvzRlGB9TIxYyZsccKhB3v1dv/rlQlv+1T86yLcY54roE2eMH8UmL93YvOwCaMRUQ5CU 45NodqiwQbNfkFXtAlXtz4Skxg9ss9l1y3EGAhsgOqkgWZI3tq+sWlcGscxGQfk2l4I4 awfDcODuDFS35tGemQBed1cxMSXcKBv1UC817KqQfsQJoNNoxu1WV0B93KUa2pX2MhOT gjBqpE31eZKTM3T1JefVI0DT4DQRx/tqh+lGpJJT9IiYndAi6jzAZOpycfxG2494vbyp oSng== X-Received: by 10.194.243.226 with SMTP id xb2mr27960125wjc.67.1374683140536; Wed, 24 Jul 2013 09:25:40 -0700 (PDT) Received: from [192.168.0.12] (gou06-3-88-170-165-56.fbx.proxad.net. [88.170.165.56]) by mx.google.com with ESMTPSA id w4sm6328075wia.9.2013.07.24.09.25.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Jul 2013 09:25:39 -0700 (PDT) Sender: Thomas Gazagnaire Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Thomas Gazagnaire In-Reply-To: Date: Wed, 24 Jul 2013 18:25:37 +0200 Cc: Gerd Stolpmann , Fabrice Le Fessant , Francois Berenger , Ocaml Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: References: <1374669368.25411.5@samsung> <1B6BB035-9909-4F0C-9DEA-F713B977A467@ocamlpro.com> To: Markus Mottl X-Mailer: Apple Mail (2.1085) Subject: Re: AW: [Caml-list] GODI is shutting down > Oasis may are may not become the standard OCaml package specification > tool, but it is widely used so I think it's fair if it is better > supported by OPAM than alternatives. Right, this is indeed a feature requested by many people, than I can hear. = This is tracked and discussed in [1] and I'm fine to try to implement the p= roposed solution in 1.1 (I've just updated the issue's release target). [1] https://github.com/OCamlPro/opam/issues/156 > It really shouldn't be that hard to automate the > process of updating OPAM metadata (including version constraints) > based on changes in Oasis package specifications. A substantial amount of work has already been done by Christophe Troestler = to automate the conversion of _oasis into OPAM files: $ opam install oasis2opam I'm sure this can be completed to automate the pull-request machinery as we= ll. However, the main problem (the one I wanted to point out) still remains: ev= ery time you want to fix a constraint you have to change your _oasis, modif= y the package tarball, and make a new release -- which means you can never = fix constraints on already released packages. But I guess in this case, it'= s fine if the _oasis and OPAM files are not in sync. [2] https://github.com/ocaml/oasis2opam -- Thomas