caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David CHEMOUIL <David.Chemouil@onera.fr>
To: caml-list@inria.fr
Subject: [Caml-list] releasing and publishing an OCaml program
Date: Fri, 16 Oct 2015 20:24:16 +0200	[thread overview]
Message-ID: <6f77545c62146e8d504a5117716d7d1f@sybille.onecert.fr> (raw)

Hi,

I am looking for a self-contained, to the point, documentation or 
tutorial detailing steps, or even commands and scripts to run in order 
to release and publish an OCaml-programmed piece of software.

I guess it partly depends on one's way to develop and organize his or 
her code base. Still I also guess there are common steps followed by a 
fair amount of people.

As far as we are concerned for our project, we rely on OCaml code 
solely, plus Opam-installed tools (e.g. Menhir) and libraries; plus 
Oasis and Ocamlbuild. Our development is hosted on a Git repo.

So common tasks we'd like to automate are quite simple: adding the 
commit number and/or a build number in the OCaml source code (e.g. to 
display it when running the program), to display a git tag corresponding 
perhaps to a human-readable version number, publishing the progam on 
Opam, maybe even publishing a compiled version as a Debian package... As 
far as possible we'd like to avoid reinventing the wheel as well as 
duplicating information already present in a file (e.g. the _oasis file 
contains some data).

After some web searching, I was able to find real projects as examples 
as well as some partial (good) tutorials but it would be nice if there 
was a single documentation or bunch of scripts to address these rather 
common requirements.

Best

dc

-- 
David Chemouil // Onera/DTIM Toulouse // tel:+33-5-6225-2936
<http://www.onera.fr/staff/david-chemouil>


             reply	other threads:[~2015-10-16 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 18:24 David CHEMOUIL [this message]
2015-10-16 19:29 ` Basile Starynkevitch
2015-10-17  7:22   ` Gabriel Scherer
2015-10-17 17:25     ` Ashish Agarwal
2015-10-17 19:42     ` ygrek
2015-10-19  8:50       ` Kenneth Adam Miller

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=6f77545c62146e8d504a5117716d7d1f@sybille.onecert.fr \
    --to=david.chemouil@onera.fr \
    --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).