From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.9 required=5.0 tests=AWL,SPF_NEUTRAL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id BC757BC6D for ; Tue, 29 Jan 2008 19:02:22 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAKr4nkfAXQInh2dsb2JhbACQHgEBAQgKKZddhyE X-IronPort-AV: E=Sophos;i="4.25,270,1199660400"; d="scan'208";a="6712978" Received: from concorde.inria.fr ([192.93.2.39]) by mail2-smtp-roc.national.inria.fr with ESMTP; 29 Jan 2008 19:02:22 +0100 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id m0TI2CW0028171 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Tue, 29 Jan 2008 19:02:22 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAACP5nkdC+Vyulmdsb2JhbACQHgEBAQEHBAYiB5dhhyE X-IronPort-AV: E=Sophos;i="4.25,270,1199660400"; d="scan'208";a="21946503" Received: from ug-out-1314.google.com ([66.249.92.174]) by mail4-smtp-sop.national.inria.fr with ESMTP; 29 Jan 2008 19:02:21 +0100 Received: by ug-out-1314.google.com with SMTP id k40so212071ugc.18 for ; Tue, 29 Jan 2008 10:02:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; bh=ZrXbmJ70W541SZ66qq1CuJmBnRQ7k49bd8bEKhIOFqs=; b=QbtmZdfpAhFlWHqMw+t9Q4a4ih7oAHFWZbOS2Sw0YleHo6IscXX6vAi6QRgaqW/+h9h2UrnBC5HXn6smxNj/VWxF/LoRpiaj7RV8toB/Kkw6qguU9AtbQxAzt74tBUfRxtudxyLau1A+wj76tN5+ZfPk9j8i7tqlfQRoYXpLfVI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; b=F/zawVS00IESs/vL/yB8irtinSbr3kohxIr9vr8SUjEw9eKd/SDZIMo2cCpX8X01dpi4b2GCQbt6ZRFsV4O2w6XzRMMrR0nf4TRkSUVcTzpJs/b6UJtrj1u0iNVuNvlMD9ZkEdj8j+FMQmkaEuP7Ec8etcHTxE1Ywjm9fouk+Hc= Received: by 10.67.26.7 with SMTP id d7mr1722960ugj.23.1201629740862; Tue, 29 Jan 2008 10:02:20 -0800 (PST) Received: from ?192.168.3.139? ( [85.2.26.102]) by mx.google.com with ESMTPS id 34sm1204036ugh.40.2008.01.29.10.02.20 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Jan 2008 10:02:20 -0800 (PST) Cc: yminsky@gmail.com, Caml-list List Message-Id: From: =?ISO-8859-1?Q?B=FCnzli_Daniel?= To: Berke Durak In-Reply-To: <479F63CC.60004@exalead.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v915) Subject: Re: [Caml-list] [OSR] Ports-like package management system Date: Tue, 29 Jan 2008 19:02:22 +0100 References: <479F0664.2070706@exalead.com> <891bd3390801290511q29ab5fd4y78ee6d8614461487@mail.gmail.com> <479F63CC.60004@exalead.com> X-Mailer: Apple Mail (2.915) Sender: =?ISO-8859-1?Q?Daniel=20B=FCnzli?= X-Miltered: at concorde with ID 479F6A24.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; bunzli:01 buenzli:01 berke:01 durak:01 c-v:01 c-v:01 dependencies:01 a's:01 sunk:98 pray:98 caml-list:01 precisely:01 override:03 daniel:04 daniel:04 Le 29 janv. 08 =E0 18:35, Berke Durak a =E9crit : >> It would also be nice to have a set of versions of the various =20 >> libraries that hang together, as GODI does. Otherwise, problems in =20= >> the case where there are packages A, B and C where A depends on B =20 >> and C and B depends on C. You need a version of C that works with =20= >> your versions of A and B, or you're sunk. So some central repo =20 >> where you can maintain a set of "safe" versions would allow for a =20 >> developer to ask for a easily pull a collection of working libraries. > > I recommend the use of a VCS precisely for that kind of thing: to =20 > be able to depend on an exact revision. This won't solve the problem per se. If you have : A-v1 depends on C-v1 B-v1 depends on C-v2 You need a way to be able to tell A-v1 to use C-v2 (or B-v1 to use C-=20= v1). So that you can use both A-v1 and B-v1 toghether. In a =20 distributed setting you need a way to override the dependencies and =20 pray that it works and if it doesn't contact the A's developer to =20 release a new version that works with C-v2. Again this has nothing to do with the use of a vcs. Daniel