caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Hezekiah M. Carty" <hez@0ok.org>
To: Simon Cruanes <simon.cruanes.2007@m4x.org>
Cc: David Allsopp <dra-news@metastack.com>, OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Project hosting for new OCaml projects
Date: Wed, 5 Mar 2014 13:00:40 -0500	[thread overview]
Message-ID: <CAMfPyLAQ1nCQKA=ec3nWKiTXCgftF4z7dVM_KK1Dfk0hB_fNZQ@mail.gmail.com> (raw)
In-Reply-To: <20140305152430.GJ17955@emmental.inria.fr>

On Wed, Mar 5, 2014 at 10:24 AM, Simon Cruanes
<simon.cruanes.2007@m4x.org> wrote:
>
> >
> > It seems that the following are worth doing:
> >
> > * Support OASIS (and in so doing, I believe that will migrate its build
> > system to ocamlbuild)
>
> oasis is very nice in that it centralizes, in a single _oasis file,
> everything about the project. In particular, it deals with the META file,
> building cmxa, cma, cmxs, etc. It can generate a "configure" and a
> Makefile (if you so wish), points to the documentation, the VCS
> repository, deals with several libraries (or sub-libraries, see how lwt
> does it for instance) and executables, etc.
>
> > * Support OPAM (which looks incredibly straightforward - being primarily a
> > Windows user, the OPAM typhoon has flowed past me thus far)
>
> Pretty simple indeed, 3 small files in the opam-repository and you're done.
> Also the opam team is quite reactive and helpful with packaging
> problems.
>

An additional small benefit to using oasis - oasis2opam, which is
installable from opam, allows you to automatically generate opam
metadata from your project's _oasis file.  Writing out the three opam
files by hand is simple, oasis2opam makes it even easier.

Hez

  parent reply	other threads:[~2014-03-05 18:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 15:13 David Allsopp
2014-03-05 15:24 ` Simon Cruanes
2014-03-05 15:33   ` Yotam Barnoy
2014-03-05 18:00   ` Hezekiah M. Carty [this message]
2014-03-06  1:58     ` Francois Berenger
2014-03-05 20:00 ` Daniel Bünzli
     [not found]   ` <20140305.211003.1668243541649395876.Christophe.Troestler@umons.ac.be>
2014-03-06  9:48     ` Daniel Bünzli
2014-03-06 11:55       ` Sylvain Le Gall
2014-03-06 12:05         ` Daniel Bünzli
2014-03-06  0:20 ` 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='CAMfPyLAQ1nCQKA=ec3nWKiTXCgftF4z7dVM_KK1Dfk0hB_fNZQ@mail.gmail.com' \
    --to=hez@0ok.org \
    --cc=caml-list@inria.fr \
    --cc=dra-news@metastack.com \
    --cc=simon.cruanes.2007@m4x.org \
    /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).