From: Romain Beauxis <toots@rastageeks.org>
To: caml-list@yquem.inria.fr
Subject: Ocamlcore.org: Discussions place, and requirements
Date: Fri, 1 Feb 2008 13:36:09 +0100 [thread overview]
Message-ID: <200802011336.09562.toots@rastageeks.org> (raw)
Hi all !
I have two question related to the recent discussions around ocaml community.
First of all, I'd like to know if we should continu discussing here, or we
better switch to a new mailing list.
There's a mailman almost ready on ocamlcore.org, so perhaps it should be
better to continue on a mailing list there ?
Second questions is ocaml modules that we are going to distribute there.
While we have discussed that different way we could use to collect projects
from different places, I don't think we discussed the minimal support that
the module should provide when it comes to installing and registering the
module.
For instance, all perl modules on CPAN share a common build and install
system, the same for PHP pear and etc..
This can be a real trouble sometimes, like for the xml-light parser: while it
does not support ocamlfind, the debian package added it, which I think is
fine. But, our configure script detects xml-light based on ocamlfind, so it
is screwed up when users want to build the software but installed xml-ligth
from upstream tarball...
I would recommend that we agreee on a minimal support the a module should ship
to be part of ocamlcore.org.
My point would be that it should provide a META file that should work with
ocamlfind.
Others might have a better idea, but it would be nice to choose something,
don't you think ?
Then, we should also provide templates for doing so. We have templates for
configure+ocamlfind which works for all our bindings...
Romain
next reply other threads:[~2008-02-01 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 12:36 Romain Beauxis [this message]
2008-02-01 12:48 ` Sylvain Le Gall
2008-02-01 13:27 ` [Caml-list] " Pietro Abate
2008-02-02 2:05 ` Romain Beauxis
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=200802011336.09562.toots@rastageeks.org \
--to=toots@rastageeks.org \
--cc=caml-list@yquem.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