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 mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 070D981799 for ; Wed, 24 Jul 2013 18:39:18 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of markus.mottl@gmail.com) identity=pra; client-ip=74.125.82.182; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="markus.mottl@gmail.com"; x-sender="markus.mottl@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of markus.mottl@gmail.com designates 74.125.82.182 as permitted sender) identity=mailfrom; client-ip=74.125.82.182; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="markus.mottl@gmail.com"; x-sender="markus.mottl@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-we0-f182.google.com) identity=helo; client-ip=74.125.82.182; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="markus.mottl@gmail.com"; x-sender="postmaster@mail-we0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnEDAAsC8FFKfVK2jWdsb2JhbABQCoM7UL1dBAGBDggWDgEBAQEHCwsJEgYkgiQBAQVAARQHHQEDDAYFCw0uIQEBEQEFARwGEwgTh2IBAw+bQoxPgn+ETAoZJw1kh3QBBQyNCYEvIWUzB4QAA5V2gWmMJ4NBFimEViA X-IPAS-Result: AnEDAAsC8FFKfVK2jWdsb2JhbABQCoM7UL1dBAGBDggWDgEBAQEHCwsJEgYkgiQBAQVAARQHHQEDDAYFCw0uIQEBEQEFARwGEwgTh2IBAw+bQoxPgn+ETAoZJw1kh3QBBQyNCYEvIWUzB4QAA5V2gWmMJ4NBFimEViA X-IronPort-AV: E=Sophos;i="4.89,736,1367964000"; d="scan'208";a="22151087" Received: from mail-we0-f182.google.com ([74.125.82.182]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 24 Jul 2013 18:39:17 +0200 Received: by mail-we0-f182.google.com with SMTP id u55so3796949wes.13 for ; Wed, 24 Jul 2013 09:39:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=2LtTyq7nawmR8IZh0aRuUpc38942SOOHq0cA6uaq/eY=; b=w10AbOnvSA7g2hMr0LptM3DNfs4t0gSG5YK+HYPtSpM9MoqmqYwxUc+XrqrvZNn/M/ am2BDmBsW2uiUJ6j/xYuIcXP0MjVM8nI+obR3811x10salG/EL/x1YIgEr7A2KglBALe fDutyn+RRMreAzRSrgAHqUDuAIp8urIqIyTyFm82dgjUSrNCkjpVgdrt4jwlOBK+RD5w B5A8KPyZCZbkeGvLhYoockW5P+rC2LN5Un7207+NwCWWpmiwtg8rlcJwaCLJy784EslA T2u4V0pvyxeptNkpATsK/OlJpVgr7HQ7KGfGRCHN5eaxpNWuDYFDY1R1ts1pm+f8FC5f cNGg== MIME-Version: 1.0 X-Received: by 10.194.108.132 with SMTP id hk4mr27747910wjb.43.1374683957095; Wed, 24 Jul 2013 09:39:17 -0700 (PDT) Received: by 10.194.172.169 with HTTP; Wed, 24 Jul 2013 09:39:17 -0700 (PDT) In-Reply-To: References: <1374669368.25411.5@samsung> <1B6BB035-9909-4F0C-9DEA-F713B977A467@ocamlpro.com> Date: Wed, 24 Jul 2013 12:39:17 -0400 Message-ID: From: Markus Mottl To: Thomas Gazagnaire Cc: Gerd Stolpmann , Fabrice Le Fessant , Francois Berenger , Ocaml Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: AW: [Caml-list] GODI is shutting down On Wed, Jul 24, 2013 at 12:25 PM, Thomas Gazagnaire w= rote: > 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, mod= ify the package tarball, and make a new release -- which means you can neve= r fix constraints on already released packages. But I guess in this case, i= t's fine if the _oasis and OPAM files are not in sync. The way I see it is that a package that contains incorrect dependency information, even if it's just a version thing, has a bug and should be fixed. I agree this is annoying to package developers, but fixing bugs is always annoying ;-) I don't see a conflict with OPAM allowing you to fix dependency information just within OPAM. Maybe there should be some special syntax to identify overrides to constraints for certain package versions so that corrected version constraints will eventually be picked up from fixed packages again. In the long run my preferred solution is to fix the cause of a problem, not to use band aids to cover up symptoms. Regards, Markus -- Markus Mottl http://www.ocaml.info markus.mottl@gmail.com