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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 145F581799 for ; Thu, 25 Jul 2013 23:01:09 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of adrien@notk.org designates 91.121.71.147 as permitted sender) identity=mailfrom; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhQFAJ6R8VFbeUeT/2dsb2JhbABagwaDKGm6VYEXFnSCJQEFI1YQCxoCBRMOAgIPBRgxiCenZZFDgSiOVQeCXzNuA5deAZFNgxY6 X-IPAS-Result: AhQFAJ6R8VFbeUeT/2dsb2JhbABagwaDKGm6VYEXFnSCJQEFI1YQCxoCBRMOAgIPBRgxiCenZZFDgSiOVQeCXzNuA5deAZFNgxY6 X-IronPort-AV: E=Sophos;i="4.89,745,1367964000"; d="scan'208";a="27346455" Received: from nautica.notk.org ([91.121.71.147]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 25 Jul 2013 23:01:08 +0200 Received: by nautica.notk.org (Postfix, from userid 1003) id 0A81EC009; Thu, 25 Jul 2013 23:01:08 +0200 (CEST) Date: Thu, 25 Jul 2013 23:01:08 +0200 From: Adrien Nader To: Daniel =?utf-8?Q?B=C3=BCnzli?= Cc: Ocaml Mailing List Message-ID: <20130725210107.GB15673@notk.org> References: <1374669368.25411.5@samsung> <1B6BB035-9909-4F0C-9DEA-F713B977A467@ocamlpro.com> <7F8931D5-E65D-49EB-B54D-A50716F3EFDD@recoil.org> <20130725053212.GB2066@notk.org> <8FEB708CF46449F1A7E7E03BCEF48718@erratique.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <8FEB708CF46449F1A7E7E03BCEF48718@erratique.ch> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: [Caml-list] GODI is shutting down Hi, I've been told on IRC that I had completely failed at explaining my thoughts so I'll skip answering to your objections and try again. Sorry for that, it was still a bit early and I didn't plan well the time needed to proofread properly. Oasis is completely independant of the package manager. It helps build something that can be easily packaged but it doesn't go further, except maybe by providing some helpers but that's a very small part of oasis. It also setups the build system and opam doesn't do that. Opam only works in your case because you've written a working build script but that's not something easy and that's something that most usually failed. It helps with the more complex builds, including C bindings. There were mentions of it being an issue for bigger projects, I'm (geniously) curious about them: what and how? There's some overlap between oasis and your-build-scripts+opam but oasis and opam simply aren't the same. By the way, you should expect additional complexity soon as cross-compilation becomes possible without additional patches to the compiler. That's something a system like oasis could take care of. I've cross-compiled libraries relying on oasis without issue by changing ocamlfind's configuration. I'm under the impression oasis doesn't differentiate yet between tools that need to run on the build and on the host system (autotools parlance) but that would be easy even without changing _oasis files with simple heuristics. -- Adrien Nader