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 D625381799 for ; Wed, 24 Jul 2013 03:55:16 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of berenger@riken.jp) identity=pra; client-ip=134.160.33.176; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of berenger@riken.jp designates 134.160.33.176 as permitted sender) identity=mailfrom; client-ip=134.160.33.176; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of postmaster@postman.riken.jp designates 134.160.33.176 as permitted sender) identity=helo; client-ip=134.160.33.176; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="postmaster@postman.riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AggCAPAy71GGoCGwnGdsb2JhbABbgzuDWb1kgSoOAQEBAQEICwkJFCiCJAEBBAEjFUAGCwsYAgIFFgsCAgkDAgECAUUTCAEBiAYGpmuROoEojlwWgkmBIQOJKI43hiOOTQ X-IPAS-Result: AggCAPAy71GGoCGwnGdsb2JhbABbgzuDWb1kgSoOAQEBAQEICwkJFCiCJAEBBAEjFUAGCwsYAgIFFgsCAgkDAgECAUUTCAEBiAYGpmuROoEojlwWgkmBIQOJKI43hiOOTQ X-IronPort-AV: E=Sophos;i="4.89,731,1367964000"; d="scan'208";a="22064000" Received: from postman4.riken.jp (HELO postman.riken.jp) ([134.160.33.176]) by mail3-smtp-sop.national.inria.fr with ESMTP; 24 Jul 2013 03:55:15 +0200 Received: from postman.riken.jp (postman4.riken.jp [127.0.0.1]) by postman.riken.jp (Postfix) with SMTP id B0A37828123 for ; Wed, 24 Jul 2013 10:55:10 +0900 (JST) Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98]) by postman.riken.jp (Postfix) with ESMTPA id 7D3B97F803E for ; Wed, 24 Jul 2013 10:55:10 +0900 (JST) Message-ID: <51EF33FE.2060407@riken.jp> Date: Wed, 24 Jul 2013 10:55:10 +0900 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 MIME-Version: 1.0 To: caml-list@inria.fr References: <1e141e2803d9dec6a8231dd4f16dd173.squirrel@gps.dynxs.de> <20130723090713.GA9274@notk.org> In-Reply-To: <20130723090713.GA9274@notk.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.7.24.14521 Subject: Re: [Caml-list] GODI is shutting down On 07/23/2013 06:07 PM, Adrien Nader wrote: > Hi, > [...] > To be honest, I've never understood why opam was "started". Contracted development, I guess. > I believe > the time would have been much better spent improving godi. Really? So, when you start to dive in a large codebase, you think you have: - full control - deep understanding - can do dramatic changes easily (like using state of the art dependency resolution technology) I personally think it is good to start from scratch, sometimes. In the long run, it can be a winning strategy. > I've heard complaints against the UI and the package release process of > godi. > How can such complaints about the UI be a reason to start a new > project?! Couldn't the package release process be improved gradually? Some people also started another package manager before OPAM went public, if you want to know. It was called odb.ml. cf. https://github.com/thelema/odb Maybe it was just a hack, but for some people it was already filling the bill better than GODI. F. PS: I do like and use many stuffs released by Gerd: ocamlnet, ocamfind, etc.