From: bluestorm <bluestorm.dylc@gmail.com>
To: Sylvain Le Gall <sylvain@le-gall.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: [ANN] oasis v0.2.0: Architecture for building OCaml libraries and applications
Date: Fri, 22 Oct 2010 21:41:59 +0200 [thread overview]
Message-ID: <AANLkTik1qu2ctP1BZ8nxsmurcwTf4LrC_C69C0JW0r5y@mail.gmail.com> (raw)
In-Reply-To: <slrnic3jpd.r67.sylvain@gallu.homelinux.org>
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
On Fri, Oct 22, 2010 at 7:51 PM, Sylvain Le Gall <sylvain@le-gall.net>wrote:
> Have you tried the "revamped" quickstart subcommand. I am trying to make
> the creation of _oasis as easy as possible...
>
>
> If you have any suggestions to help make "lighter", I'll be happy. BTW,
> when you say "heavier", is it in term of complexity, of size of the
> generated setup.ml or something else?
I think it's mostly a question of getting used to the new features of oasis.
Oasis much more things than with a META (configuration, compilation, etc.),
so the downside is that there are more things to specify in a _oasis file
than in a META file.
During my work with various such tools (Makefile, META, etc.), I found out
that I rely strongly on example files that I can copy/paste and
modify/adapt. With time I have accumulated some templates for
Makefile/META/_tags/myocamlbuild.ml covering my basics need, and I know
where to look for more advanced things to imitate. I have not yet
accumulated a comprehensive set of reusable _oasis files (though the
documentation is certainly in the good direction), but I think it's just a
matter of time.
And before OASIS-DB, there should be "oasis bundle", that should do
> exactly what you ask me.
>
> I can try to create an experimental oasis-bundle-0.2.0.tar.gz. Will you
> test it?
>
Certainly I'd be glad to give it a try.
> It's a triviality to say but I'm quite happy with the change in
> command-line
> > invocation style (OASIS -setup => oasis setup). Four small comments
> > regarding this : [..]
>
> All this seems quite reasonable. May I ask you to submit feature
> requests about this on the BTS?
>
>
Done.
[-- Attachment #2: Type: text/html, Size: 2674 bytes --]
next prev parent reply other threads:[~2010-10-22 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 23:03 Sylvain Le Gall
2010-10-22 12:54 ` [Caml-list] " Dario Teixeira
2010-10-22 13:01 ` Sylvain Le Gall
2010-10-23 6:08 ` [Caml-list] " Mihamina Rakotomandimby
2010-10-22 17:00 ` [Caml-list] " bluestorm
2010-10-22 17:51 ` Sylvain Le Gall
2010-10-22 19:41 ` bluestorm [this message]
2010-10-22 19:50 ` Sylvain Le Gall
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=AANLkTik1qu2ctP1BZ8nxsmurcwTf4LrC_C69C0JW0r5y@mail.gmail.com \
--to=bluestorm.dylc@gmail.com \
--cc=caml-list@inria.fr \
--cc=sylvain@le-gall.net \
/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).