From: Thomas Gazagnaire <thomas@ocamlpro.com>
To: OCaml mailing-list <caml-list@inria.fr>
Cc: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Subject: [Caml-list] [RFC] new OPAM command-line interface
Date: Fri, 14 Dec 2012 19:09:40 +0100 [thread overview]
Message-ID: <E9F66D7B-A8AA-4C49-8DE9-340A3CDF4908@ocamlpro.com> (raw)
Hi,
In order to prepare the beta release of OPAM (which should hopefully be announced at the end of next week if everything goes well), I've been working on improving its command-line interface (which is currently a bit had-hoc). Thanks to the great Daniel Bunzli's cmdliner[1] library, I now have a nice -- but incompatible -- command-line interface in the 'cmdliner' branch[2].
The main changes are:
* an uniform help interface, where all flags and parameters are correctly documents
* no more -long-option, only -s or --long
* 'opam remote' is still there for convenience but will be deprecated; use 'opam repository' instead
* use of sub-sub-commands when necessary (ie. 'opam repository add')
* use non-ambiguous prefix of sub-command instead of the subcommand (ie. 'opam repo' or 'opam rem')
* AND: a nice 'opam --help' and 'opam <subcommand> --help' output
I'm quite keen to get community feedback on this new command-line. Feel free to comment here, or to to use the issue tracker[3].
Cheers,
Thomas
[1] http://erratique.ch/software/cmdliner
[2] git clone -b cmdliner git://github.com/OCamlPro/opam.git
[3] https://github.com/OCamlPro/opam/issues/157
next reply other threads:[~2012-12-14 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 18:09 Thomas Gazagnaire [this message]
2012-12-14 19:29 ` Wojciech Meyer
[not found] ` <28D2FDF4-81FB-4368-B331-7811DD606A0E@ocamlpro.com>
2012-12-14 23:15 ` Wojciech Meyer
2012-12-18 17:00 ` Ashish Agarwal
2013-01-03 11:26 ` [Caml-list] " Thomas Gazagnaire
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=E9F66D7B-A8AA-4C49-8DE9-340A3CDF4908@ocamlpro.com \
--to=thomas@ocamlpro.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