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 79DFFBC6C for ; Wed, 30 Jan 2008 15:35:35 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAACQaoEfAXQInh2dsb2JhbACQJwEBAQgKKZ83 X-IronPort-AV: E=Sophos;i="4.25,277,1199660400"; d="scan'208";a="7432849" Received: from concorde.inria.fr ([192.93.2.39]) by mail1-smtp-roc.national.inria.fr with ESMTP; 30 Jan 2008 15:35:35 +0100 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id m0UEZY5p000394 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Wed, 30 Jan 2008 15:35:35 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAN4ZoEdQW+UCh2dsb2JhbACQJwEBAQgKKZ8z X-IronPort-AV: E=Sophos;i="4.25,277,1199660400"; d="scan'208";a="8539692" Received: from main.gmane.org (HELO ciao.gmane.org) ([80.91.229.2]) by mail3-smtp-sop.national.inria.fr with ESMTP; 30 Jan 2008 15:35:32 +0100 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JKE2F-00049m-Tg for caml-list@inria.fr; Wed, 30 Jan 2008 14:35:31 +0000 Received: from ks300734.kimsufi.com ([91.121.65.225]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 30 Jan 2008 14:35:31 +0000 Received: from sylvain by ks300734.kimsufi.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 30 Jan 2008 14:35:31 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: caml-list@inria.fr From: Sylvain Le Gall Subject: Re: [OSR] Ports-like package management system Date: Wed, 30 Jan 2008 14:35:26 +0000 (UTC) Message-ID: References: <479F0664.2070706@exalead.com> <47A045C1.7030603@exalead.com> <47A05C59.2070900@exalead.com> <47A08895.80301@exalead.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ks300734.kimsufi.com User-Agent: slrn/0.9.8.1pl2 (Debian) Sender: news X-Miltered: at concorde with ID 47A08B36.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; le-gall:01 berke:01 durak:01 berke:01 durak:01 packager:01 bug:01 ocaml:01 wrote:01 tree:02 module:03 patches:03 patches:03 commit:03 repository:03 On 30-01-2008, Berke Durak wrote: > Sylvain Le Gall a écrit : >>> We are not forcing anyone to work using the selected VCS. We are just >>> asking them to regularly publish their software to the VCS. If they >>> directly work using the selected VCS, publishing commits will be easier >>> for them - but they can still work on a day-to-day basis using their own >>> VCS. >>> >> >> Do they have to merge their changes with packager changes? In this case, >> i really do think that upstream author won't publish their changes a >> lot. > > If they are using VCS2 for working, they just have to commit their changeset to > some VCS repository from time to time. This repository can be hosted by anyone. > There won't be a mandatory central repository. > > Example 1: Alphonse uses Darcs to develop Nicemodule. He sets up a VCS repository > (say, Mercurial, if we agree on mercurial) repository on his server. He adds the > required opkg files in his source tree. Once in a while he commits Nicemodule to > his Mercurial repository, but keeps working on Darcs. Bernard checks out the > Mercurial and sends a patch P against the Mercurial version. > Not sure it will work in most case. > Example 2: Alphonse doesn't want to use opkg or mercurial, but is the author of > a really nice module Nicemodule. Bernard sets up a Mercurial repository where he imports > Alphonse's Nicemodule and adds opkg information. Opkg users can then use Nicemodule > by simply writing require(nicemodule). Bernard tracks Alphonse's source > code and sends him back patches against his code. > I think this should be an option. The only things is that Bernard must continue to send patches to Alphonse... > Example 3: Alphonse finally sees that using the same VCS as everyone else has more > benefits than the extra niceness his preferred VCS has. His changes will be visible > immediately in the Opkg system and he will be able to pull patches from his friends > easily. He therefore uses Opkg and its associated VCS right from the start for > his new project. When he has a new stable release, he simply tags it and adds a line > in the release file. When Bernard starts developing a feature Y, he can directly pull > Alphonse's changes and push back bug fixes. Stop dreaming ;-) (i.e. Alphonse and Bernard keep talking about VCS, Alphonse and Bernard decide to both start a new VCS from scratch, in OCaml, nobody works anymore on Nicemodule). Regards, Sylvain Le Gall