From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 0535681799 for ; Wed, 24 Jul 2013 20:49:51 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of markus.mottl@gmail.com) identity=pra; client-ip=209.85.212.170; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="markus.mottl@gmail.com"; x-sender="markus.mottl@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of markus.mottl@gmail.com designates 209.85.212.170 as permitted sender) identity=mailfrom; client-ip=209.85.212.170; receiver=mail2-smtp-roc.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 (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wi0-f170.google.com) identity=helo; client-ip=209.85.212.170; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="markus.mottl@gmail.com"; x-sender="postmaster@mail-wi0-f170.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnEDADQh8FHRVdSqjWdsb2JhbABagztQvV4EAYEOCBYOAQEBAQcLCwkSBiSCJAEBBQw0ARQHHQEDDAYFCw0uIQEBEQEFARwGE4d9AQMPm2aMT4J/hFMKGScNZId0AQUMjQmBKSdlMweEAAOVdoFpjCeDQRYphFYggTU X-IPAS-Result: AnEDADQh8FHRVdSqjWdsb2JhbABagztQvV4EAYEOCBYOAQEBAQcLCwkSBiSCJAEBBQw0ARQHHQEDDAYFCw0uIQEBEQEFARwGE4d9AQMPm2aMT4J/hFMKGScNZId0AQUMjQmBKSdlMweEAAOVdoFpjCeDQRYphFYggTU X-IronPort-AV: E=Sophos;i="4.89,736,1367964000"; d="scan'208";a="27202308" Received: from mail-wi0-f170.google.com ([209.85.212.170]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 24 Jul 2013 20:49:50 +0200 Received: by mail-wi0-f170.google.com with SMTP id ey16so5511660wid.5 for ; Wed, 24 Jul 2013 11:49:50 -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=YGLGrIdJBOZ/+6MZphS0ryP5k64PvEEqNwWXDDNriUA=; b=b94LDA0D4hWN1aws6etgIESs8OR1YzqquE3w8HaIvHT8CCgo+vw/B2WQ2iqCGUbNZm RV/5a1W/xxsL1r8Pf2sGGvSF9Pxt/7w6xno1m6j8bcdW0wNx+yHC3D6PdNv/39w1TKsh wX4EhG09IqGaz10TCZSxLFhRcWiYpqCKoTpRKz9ApKT2ap/oMnmaWk1U0OXe/1emlTTQ LuClPkGm5+ixA7OT1EJfowR4pxlCDmc5RYNljl2rk1xW5xfCYztSalteIKeIDdR75Rt8 typGK293w9Bn6x72AxwB4+WzKav5HSb/EDKqcOoc6hy1mUj6MXAeAg7sD3Dbg5Vb8lUr CATg== MIME-Version: 1.0 X-Received: by 10.194.122.103 with SMTP id lr7mr27941876wjb.15.1374691790223; Wed, 24 Jul 2013 11:49:50 -0700 (PDT) Received: by 10.194.172.169 with HTTP; Wed, 24 Jul 2013 11:49:50 -0700 (PDT) In-Reply-To: <51F00FD0.9090402@etorok.net> References: <1374669368.25411.5@samsung> <1B6BB035-9909-4F0C-9DEA-F713B977A467@ocamlpro.com> <1D7F094E-0380-4D11-97BD-F047C57AB331@ocamlpro.com> <51F00FD0.9090402@etorok.net> Date: Wed, 24 Jul 2013 14:49:50 -0400 Message-ID: From: Markus Mottl To: =?ISO-8859-1?Q?T=F6r=F6k_Edwin?= Cc: caml-list@inria.fr 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 1:33 PM, T=F6r=F6k Edwin wrote: > That is a bug in package B, and should be addressed before making v1.1 av= ailable in the main repository: > 1) either update version constraints of A as you suggest directly in opam > 2) fix package B to be backwards compatible (or at least report a bug up= stream about it) > 3) do as in #1, i.e. use opam file as authoritative source, but report a= bug against package A with a patch to _oasis, and a request to regenerate = the files. The bugreport could even be automated (I assume package maintain= ers are automatically notified of bugs in their packages as well?) > > There is also the possibility to automatically run 'oasis setup' for usua= l packages (that don't need special OASIS plugins and so on), and include t= he generated files as patches ... automatically. I think we will have to accept that on some level specified version constraints are not authoritative. Just because I specify in my package that library A is compatible with whatever version of library B doesn't make it so. Incompatibilities may not show up during build time, may elude all test suites, and still make your program bomb. Full automation is hence impossible, though at least the build part and test suite part could in principle be covered automatically. This means that a good packaging system will have to be able to override version constraints that are specified by a particular package version to exclude individual versions of dependencies or ranges thereof. Of course, such overrides should eventually be communicated back to the package maintainer. This communication can be automated: just send an email to the specified package maintainer each time constraint overrides are added or changed, no matter whether automatically or manually. Regards, Markus -- Markus Mottl http://www.ocaml.info markus.mottl@gmail.com