From: Dagnat Fabien <fabien.dagnat@telecom-bretagne.eu>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] man, doc, … and opam
Date: Fri, 5 Jul 2013 17:58:29 +0200 [thread overview]
Message-ID: <8D4165F2-D097-4497-AD9F-18AFA1E21266@telecom-bretagne.eu> (raw)
Hello,
After reading the opam documentation, I'm not sure anything specific has been done about the extra resources of packages (man and doc files for example).
The only things, I found in the documentation is build-doc switch to indicate how to build the doc. For example, utop.1.5.opam contains
build-doc: [ "ocaml" "setup.ml" "-doc" ]
I was expecting to find the doc of utop but on my .opam repository, the doc directory of utop is empty. Furthermore, in the utop.install file there is no doc command.
Does it depends on how the install command have been done by the user? Have I missed something?
More generally, my question also apply to man pages not found anywhere in the opam documentation.
Fabien
next reply other threads:[~2013-07-05 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 15:58 Dagnat Fabien [this message]
2013-07-07 17:38 ` Daniel Bünzli
2013-07-08 9:56 ` Thomas Gazagnaire
2013-07-08 15:41 ` Daniel Bünzli
2013-07-08 17:18 ` Gabriel Kerneis
2013-07-08 21:10 ` Daniel Bünzli
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=8D4165F2-D097-4497-AD9F-18AFA1E21266@telecom-bretagne.eu \
--to=fabien.dagnat@telecom-bretagne.eu \
--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).