From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vb@vb.fdn.fr>
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 4372F7EEB4
	for <caml-list@sympa.inria.fr>; Sat,  2 Feb 2013 11:27:43 +0100 (CET)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  vb@vb.fdn.fr) identity=pra; client-ip=94.23.24.152;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="vb@vb.fdn.fr"; x-sender="vb@vb.fdn.fr";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  vb@vb.fdn.fr) identity=mailfrom; client-ip=94.23.24.152;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="vb@vb.fdn.fr"; x-sender="vb@vb.fdn.fr";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@luminar.eu.org) identity=helo;
  client-ip=94.23.24.152;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="vb@vb.fdn.fr";
  x-sender="postmaster@luminar.eu.org";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFACPpDFFeFxiY/2dsb2JhbABFu1mDXxZzgh8BAQUyAQVAEQsYCRYPCQMCAQIBRRMIAQGIEcIxjimDKQOcD4phgn0
X-IPAS-Result: AgAFACPpDFFeFxiY/2dsb2JhbABFu1mDXxZzgh8BAQUyAQVAEQsYCRYPCQMCAQIBRRMIAQGIEcIxjimDKQOcD4phgn0
X-IronPort-AV: E=Sophos;i="4.84,590,1355094000"; 
   d="scan'208";a="842024"
Received: from luminar.eu.org ([94.23.24.152])
  by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 02 Feb 2013 11:24:44 +0100
Received: from [192.168.1.112] (unknown [80.67.176.29])
	(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by luminar.eu.org (Postfix) with ESMTPSA id 65A0C5F750
	for <caml-list@inria.fr>; Sat,  2 Feb 2013 11:27:40 +0100 (CET)
Message-ID: <510CEA1B.2070809@vb.fdn.fr>
Date: Sat, 02 Feb 2013 11:27:39 +0100
From: "Vincent B." <vb@vb.fdn.fr>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130109 Thunderbird/17.0.2
MIME-Version: 1.0
To: caml-list@inria.fr
References: <20130131010339.0bb90e1aca528ff49339998f@gmail.com> <20130131092106.GA20713@frosties>
In-Reply-To: <20130131092106.GA20713@frosties>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Validation-by: vb@vb.fdn.fr
Subject: Re: [Caml-list] [ANN] ocurl forked and 0.5.4 released

On 31/01/2013 10:21, Goswin von Brederlow wrote:
> Can you tell us why you need to fork ocurl? Why not continue the original
> project?
>
> And if you must fork then please change the name so the two don't get
> confused.
>
> MfG
> 	Goswin

Hi,

This fork started as I (on behalf of the OPAM team) asked for a fork of 
ocurl to include in OPAM since the original ocurl has not been updated 
for a long time, and is not compiling anymore out of the box, at least 
on recent versions of OCaml. Moreover as ygrek said, his version 
accumulates lots of bugfixes meant to be integrated into the official 
branch for a long time already, that could not make it because the 
original author did not answer at all.

The need of a fork arises from what is mentionned before, mostly the 
original author being unreachable and the changes accumulating too much 
to be kept as separate patches.

As for changing the name, I would personally not do it since it is a 
rightful continuation of the ocurl project (and is backward compatible). 
I’m suggesting to wait for the original ocurl author to reappear to see 
if we can finally merge the changes.

Cheers,

Vincent