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.3 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id 83C1BBC6C for ; Wed, 30 Jan 2008 20:53:39 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAADFloEfAXQImh2dsb2JhbACQJgEBAQgKKZ91 X-IronPort-AV: E=Sophos;i="4.25,279,1199660400"; d="scan'208";a="7444484" Received: from discorde.inria.fr ([192.93.2.38]) by mail1-smtp-roc.national.inria.fr with ESMTP; 30 Jan 2008 20:53:39 +0100 Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id m0UJraVr000314 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Wed, 30 Jan 2008 20:53:39 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAPJjoEfY2tfi/2dsb2JhbACwXw X-IronPort-AV: E=Sophos;i="4.25,279,1199660400"; d="scan'208";a="6756048" Received: from tail.lionet.info ([216.218.215.226]) by mail2-smtp-roc.national.inria.fr with ESMTP; 30 Jan 2008 20:53:35 +0100 Received: from [10.72.109.162] (nat-dip4.corp.yahoo.com [207.126.230.225]) (authenticated bits=0) by tail.lionet.info (8.13.8/8.13.6) with ESMTP id m0UJrVQT069380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 30 Jan 2008 11:53:32 -0800 (PST) (envelope-from vss@73rus.com) Message-ID: <47A0D5B7.2030103@73rus.com> Date: Wed, 30 Jan 2008 11:53:27 -0800 From: Vlad Skvortsov User-Agent: Thunderbird 1.5.0.14 (Macintosh/20071210) MIME-Version: 1.0 To: Olivier Andrieu Cc: Michael Ekstrand , caml-list@inria.fr Subject: Re: [Caml-list] Re: [OSR] Ports-like package management system References: <479F0664.2070706@exalead.com> <47A045C1.7030603@exalead.com> <871w7zgtpn.fsf@jehiel.elehack.net> <95513600801301145o4a5d4096x7492655c3d05ca8c@mail.gmail.com> In-Reply-To: <95513600801301145o4a5d4096x7492655c3d05ca8c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (tail.lionet.info [216.218.215.226]); Wed, 30 Jan 2008 11:53:32 -0800 (PST) X-Miltered: at discorde with ID 47A0D5C0.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.04; andrieu:01 tarballs:01 tarballs:01 tarball:01 tarball:01 vlad:98 rus:98 git:98 merit:98 merit:98 vlad:98 rus:98 wrote:01 caml-list:01 modules:02 Olivier Andrieu wrote: >> I think that it's somewhat strange to incorporate the source for all >> packages into one massive VCS, and it looks like that's what's been >> proposed. >> >> Metadata references tarballs. >> > > Having metadata point to the upstream VCS isn't necessarily difficult, > lots of build systems support that. > It can be as simple as using the right URI: http:// ftp:// for > tarballs, svn://, hg:// git://, etc. for a VCS. > The user doesn't need to know how to operate the VCS, the build system > does this for him. > ...meaning that the user has to install *all* possible VCSs on *all* machines where an application is to be built? Looks like a maintenance nightmare to me. >> I don't see a >> whole lot of merit for hooking into upstream VCS for the general case, >> as most users will probably want to use released tarballs of >> everything except the few modules they're working on. >> > > Speaking as the author of a caml binding library that has no published > tarball, I don't see a lot of merit for preventing access to those VCS > either :) > A revision id or tag on a repository is as good as a tarball for > referencing a precise state of some software component. > This is about introducing yet another concept into the package management system, which doesn't simplify that at all. I think the system needs to use the least common denominator as a basic transport if we want it to be widely adopted. Which is, I believe, HTTP/FTP in today's world. -- Vlad Skvortsov, vss@73rus.com, http://vss.73rus.com