From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id pBAL1GZK026610 for ; Sat, 10 Dec 2011 22:01:16 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnABAPXH407RVdK2kWdsb2JhbABDqnYIIgEBAQEJCQ0HEieBcgEBAQEDEgIkCAEbHgMMBgULDQklDwISEQEFARwTCAEBHodumBAKi2SCa4QkPYhxAgUMiEeDGgSIMYxAhUuBNIZyPYQX X-IronPort-AV: E=Sophos;i="4.71,332,1320620400"; d="scan'208";a="122867176" Received: from mail-iy0-f182.google.com ([209.85.210.182]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 10 Dec 2011 22:01:10 +0100 Received: by iakl21 with SMTP id l21so540546iak.27 for ; Sat, 10 Dec 2011 13:01:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=4Tzvdq1lhQym7Oic/MMojfDUiq3LU+2xTKVqrawgIcY=; b=h6juUpZOwJEiSCF3huS3WbFUI+iU/n2ss7Q5XlKvSbvc7Ty/KO97FWw8KOE+Jb5137 AHeFnLR/fVSdfuo7FvnsFfjS9RjeTgkpU9YyHppgHr27hF/gDtg6+VZVlST09JVfHRHt VxYhRLrPUfON5caD5puZkEwwn7R/jSUsw7eyo= Received: by 10.42.163.200 with SMTP id d8mr6976369icy.41.1323550869482; Sat, 10 Dec 2011 13:01:09 -0800 (PST) Received: from [192.168.1.65] (99-121-78-10.lightspeed.lnngmi.sbcglobal.net. [99.121.78.10]) by mx.google.com with ESMTPS id r18sm6880223ibh.4.2011.12.10.13.01.07 (version=SSLv3 cipher=OTHER); Sat, 10 Dec 2011 13:01:08 -0800 (PST) Message-ID: <4EE3C892.30003@gmail.com> Date: Sat, 10 Dec 2011 16:01:06 -0500 From: Edgar Friendly User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: caml-list@inria.fr References: <4EDE33A0.6070004@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Caml-list] Some comments on recent discussions On 12/10/2011 03:32 PM, Andrei Formiga wrote: > The question is: what should be done? What must be done to enable > OASIS-DB? Sylvain has worked with me to enable auto-installation of oasis-db packages via odb[2]. There's not a large repo of packages[1], but most of it is auto-installable (run odb to get a list), as long as you have ocaml and findlib to start from. The dependencies are automatically handled and installed from source. I even have confirmation that it works under windows, although it definitely needs cygwin there. The repo could use some love with people uploading[3] new packages to it. Just provide a tarball and optionally a link to the tarball on some other website. Oasis dependencies are detected automatically, packages w/o an _oasis file need to have deps specified manually. Odb is able to install findlib-enabled projects that use ([./configure &&] make && make install), (omake && omake install) and oasis' setup.ml for building. This last option is able to execute whatever sequence of configure, make and install commands are needed for your project, without replacing the current infrastructure. Files uploaded to the repo are available with odb --unstable, they have to be manually approved to become part of the default --testing. I hope that in time, the --stable option can become default. Odb also installs by default to ~/.odb/lib. --sudo tells it to use sudo for global install, --have-perms tells it to install to the global repo without sudo. If anyone wants to auto-detect permissions on the ocamlfind global, we can get rid of --have-perms. I'm on #ocaml most of the time, and will get back to you if I'm away. Tell me how things work or don't. E. [1] http://oasis.ocamlcore.org/dev/browse [2] http://github.com/thelema/odb [3] http://oasis.ocamlcore.org/dev/upload