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 CA0F381799 for ; Thu, 25 Jul 2013 17:29:28 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of lpw25@cam.ac.uk) identity=pra; client-ip=131.111.8.152; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="lpw25@cam.ac.uk"; x-sender="lpw25@cam.ac.uk"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of lpw25@cam.ac.uk) identity=mailfrom; client-ip=131.111.8.152; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="lpw25@cam.ac.uk"; x-sender="lpw25@cam.ac.uk"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@ppsw-52.csi.cam.ac.uk) identity=helo; client-ip=131.111.8.152; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="lpw25@cam.ac.uk"; x-sender="postmaster@ppsw-52.csi.cam.ac.uk"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvUBAAtE8VGDbwiYnGdsb2JhbABawWiBFhYOAQEBAQEICwkJFCiCJAEBBAE6PxALISUPAQRJiB0GsUeIB499B4QAA6xB X-IPAS-Result: AvUBAAtE8VGDbwiYnGdsb2JhbABawWiBFhYOAQEBAQEICwkJFCiCJAEBBAE6PxALISUPAQRJiB0GsUeIB499B4QAA6xB X-IronPort-AV: E=Sophos;i="4.89,744,1367964000"; d="scan'208";a="27319010" Received: from ppsw-52.csi.cam.ac.uk ([131.111.8.152]) by mail2-smtp-roc.national.inria.fr with ESMTP; 25 Jul 2013 17:29:12 +0200 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from kingston.cl.cam.ac.uk ([128.232.64.15]:57724) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:lpw25) (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1V2NTc-0002S6-FG (Exim 4.80_167-5a66dd3) (return-path ); Thu, 25 Jul 2013 16:29:12 +0100 From: Leo White To: Sylvain Le Gall Cc: caml-list@inria.fr References: <1374669368.25411.5@samsung> <1B6BB035-9909-4F0C-9DEA-F713B977A467@ocamlpro.com> X-Face: "XWxb[u_Z\PA_Y?9@|IA!!+jTb(/290-*ea/Un$I0B98.$n%eL.;2w*,z]WR#T:,p[ NBd++M7l]#7zj7!{~iw $W-"/=|dVjhT[D{4~gE}gK<2`.6fs!;uqqud]vs2N/3^m7{aS1V, Date: Thu, 25 Jul 2013 16:29:12 +0100 In-Reply-To: (Sylvain Le Gall's message of "Thu, 25 Jul 2013 15:16:51 +0000 (UTC)") Message-ID: <874nbik69j.fsf@kingston.cl.cam.ac.uk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Caml-list] Re: AW: GODI is shutting down >> However, the main problem (the one I wanted to point out) still >> remains: every time you want to fix a constraint you have to change >> your _oasis, modify 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. >> > > We don't share the same POV here. If a constraints is bad it should be > fixe in the upstream version. A quick fix could be to patch it in OPAM, > but if a constraint is bad with OPAM, Debian packagers will have to do > the same kind of fix. So we should make it upsteam, not keep the fix in > OPAM. > I think that Thomas' point was that if you extract the dependecies directly from an _oasis file within the package then you can only fix dependencies in future versions of the package. So, if foo-0.5.6 has a bad dependency (extracted from the _oasis file within foo-0.5.6) making the fix upstream will only help foo-0.5.7 onwards: foo-0.5.6 will still be in the repository and its dependencies will still be incorrect. I am sure he agress that fixes should be passed upstream, but we also need to be able to correct dependencies in existing packages. Regards, Leo