From: Edgar Friendly <thelema314@gmail.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] odb questions
Date: Fri, 09 Mar 2012 11:26:26 -0500 [thread overview]
Message-ID: <4F5A2F32.4020604@gmail.com> (raw)
In-Reply-To: <425EA7ADC74C447585569243EFCF80D6@erratique.ch>
On 03/09/2012 09:26 AM, Daniel Bünzli wrote:
> Without going into the dependency resolving thing, I still think it's
> an issue. Basically with odb you don't really know what you are
> downloading.
>
http://oasis.ocamlcore.org/dev/odb/
This page shows the stable, testing and unstable versions of each
package available in odb. use --unstable or --testing to get a
non-stable version. Unstable is the newest uploaded version, testing is
the newest version I've been able to make work. Stable has all been
compiled together (sometimes there's version issues between packages).
> Didn't really think hard about it, but instead of (or complementary
> to) defining it's own key-value language odb could maybe piggyback on
> oasis files (pretty easy to parse). There's a lot of info in there
> (deps etc.).
While I agree it'd be nice to just parse oasis files, they're not nearly
as trivial to parse as the k=v format. If you can write a small enough
parser with no external deps, I'll add it to odb and use its info to
supplement the packages file.
E.
next prev parent reply other threads:[~2012-03-09 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 12:32 Daniel Bünzli
2012-03-07 14:37 ` Edgar Friendly
2012-03-07 15:47 ` Daniel Bünzli
2012-03-07 15:58 ` Edgar Friendly
2012-03-07 16:28 ` Daniel Bünzli
2012-03-09 14:26 ` Daniel Bünzli
2012-03-09 16:26 ` Edgar Friendly [this message]
2012-03-09 16:47 ` Daniel Bünzli
2012-03-08 1:02 ` Francois Berenger
2012-03-08 13:29 ` Edgar Friendly
2012-03-08 15:41 ` 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=4F5A2F32.4020604@gmail.com \
--to=thelema314@gmail.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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