From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <berenger@riken.jp>
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 250217EE6B
	for <caml-list@sympa.inria.fr>; Mon, 25 Nov 2013 13:51:22 +0100 (CET)
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.161;
  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.161 as permitted
  sender) identity=mailfrom; client-ip=134.160.33.161;
  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.161 as
  permitted sender) identity=helo; client-ip=134.160.33.161;
  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: AqQDAE1Hk1KGoCGhh2dsb2JhbABZgz+8eoFBDgEBAQgNCQcWKIIlAQEFOEARCxgJFg8JAwIBAgFFEwYCAQGHfAENvXaOH28WhB0DiUCOVIEwlBk
X-IPAS-Result: AqQDAE1Hk1KGoCGhh2dsb2JhbABZgz+8eoFBDgEBAQgNCQcWKIIlAQEFOEARCxgJFg8JAwIBAgFFEwYCAQGHfAENvXaOH28WhB0DiUCOVIEwlBk
X-IronPort-AV: E=Sophos;i="4.93,767,1378850400"; 
   d="scan'208";a="37773482"
Received: from postman1.riken.jp (HELO postman.riken.jp) ([134.160.33.161])
  by mail3-smtp-sop.national.inria.fr with ESMTP; 25 Nov 2013 13:51:20 +0100
Received: from postman.riken.jp (postman1.riken.jp [127.0.0.1])
	by postman.riken.jp (Postfix) with SMTP id 3408332C0138
	for <caml-list@inria.fr>; Mon, 25 Nov 2013 21:51:16 +0900 (JST)
Received: from fbrs-iMac.local (usr013.bb802-01.ual.im.wakwak.ne.jp [219.121.104.207])
	by postman.riken.jp (Postfix) with ESMTPA id 9B42E32A0090
	for <caml-list@inria.fr>; Mon, 25 Nov 2013 21:51:15 +0900 (JST)
Message-ID: <529347C2.3000202@riken.jp>
Date: Mon, 25 Nov 2013 21:51:14 +0900
From: Francois Berenger <berenger@riken.jp>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: caml-list@inria.fr
References: <20131125031021.384845a8@kiwi.local.tld> <20131125191546.08a22f18@kiwi.local.tld>
In-Reply-To: <20131125191546.08a22f18@kiwi.local.tld>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.25.123914
Subject: Re: [Caml-list] extlib 1.6.0 released

On 11/25/13, 8:15 PM, ygrek wrote:
> On Mon, 25 Nov 2013 03:10:21 +0800
> ygrek <ygrek@autistici.org> wrote:
>
>>   * Install additionally `extlib_min` with reduced set of modules (to mitigate linking conflicts)
>
> After some more thought I don't really like this approach.
> See the reasoning in http://code.google.com/p/ocaml-extlib/issues/detail?id=23#c6
> The new approach (implemented in svn) is to include offending modules conditionally during extlib build
> time, so that extlib without UChar module can be easily integrated into codebases that don't depend on UChar,
> while others may take some time to amend the code. Basically the decision is being retargeted
> from code developer to the end-user/admin. Cursory research suggests that in opam there is one package
> using UTF8 module from extlib - namely javalib. So practically it means creating
> two opam packages extlib and extlib_full and promoting the first. This sounds better than having
> two ocamlfind packages, anyway.
> What do you think?

I even wonder why extlib is still out there.
I was thinking it was superseded by batteries.