caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: caml-list@inria.fr
Subject: Re: [Caml-list] oasis & macosx
Date: Wed, 20 Apr 2011 17:58:02 +0100	[thread overview]
Message-ID: <BANLkTinOtf+c=Vdm_Th0bOFHypdZXV9+dQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikR98J7Pqw-YQWbC=QfQs3jSNDFdQ@mail.gmail.com>

On Wed, Apr 20, 2011 at 17:25, Vincent Aravantinos
<vincent.aravantinos@gmail.com> wrote:
> I wonder if you're not making a slight confusion here.
> OASIS is not meant to install the dependencies by itself: it is not GODI.
> OASIS is "just" meant to ease and standardize the installation process in an
> environment-independent way.
> Maybe it can be seen more as an ocaml-dedicated replacement for the automake
> suite.

Maybe you are right. I find the documentation around oasis and
oasis-db rather confusing.

On Wed, Apr 20, 2011 at 17:36, Andrei Formiga <andrei.formiga@gmail.com> wrote:
> Currently you have to install the dependencies, yes. I think Sylvain
> is testing GODI packages for all dependencies, so it'll probably be
> easy to install once the packages are in the current GODI tree.
> Assuming you use GODI, of course.

I don't and won't, I don't like to lag behind compiler releases.

There's something I really don't understand here. oasis and oasis-db
are supposed to be able to manage ocaml packages. I don't wan't to
install another package manager to install the package manager. I also
don't understand why oasis needs findlib, since findlib manages
packages, or does ocaml-db use findlib to manage the packages ?

This is all rather confusing.

The experience I expected was, install the ocaml compilers, download
the oasis sources, compile them and that this would give me a system
to install ocaml packages and their dependencies.

> I believe it is based on the path returned by ocamlc -where

Well I don't like to believe, how packages are installed should be
documented somewhere. When things break you want to understand these
things.

Best,

Daniel

  reply	other threads:[~2011-04-20 16:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 15:53 Daniel Bünzli
2011-04-20 15:55 ` Joel Reymont
2011-04-20 16:12   ` Daniel Bünzli
2011-04-20 16:17     ` Joel Reymont
2011-04-20 16:25       ` Török Edwin
2011-04-20 23:38         ` Edgar Friendly
2011-04-20 16:25     ` Vincent Aravantinos
2011-04-20 16:36     ` Andrei Formiga
2011-04-20 16:58       ` Daniel Bünzli [this message]
2011-04-20 17:10         ` Andrei Formiga
2011-04-21  5:58       ` ygrek
2011-04-21  6:00         ` ygrek
2011-04-21  8:55 ` [Caml-list] " Sylvain Le Gall
2011-04-21 16:42   ` Daniel Bünzli
2011-04-21 17:02     ` dmitry grebeniuk
2011-05-19  9:29     ` Sylvain Le Gall
2011-05-30 11:04       ` Daniel Bünzli
2011-05-30 11:17         ` Gabriel Scherer
     [not found]         ` <BANLkTim1wCTkwCNZVh_VMYFNa=wkFvCuFA@mail.gmail.com>
2011-05-30 11:47           ` Daniel Bünzli
2011-05-30 13:54             ` Till Varoquaux
2011-05-30 14:06               ` Sylvain Le Gall
2011-05-30 14:56               ` Daniel Bünzli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='BANLkTinOtf+c=Vdm_Th0bOFHypdZXV9+dQ@mail.gmail.com' \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).