From: doug@bagley.org (Doug Bagley)
To: caml-list@inria.fr
Subject: [Caml-list] a question on packaging
Date: Tue, 12 Feb 2002 13:57:58 -0600 [thread overview]
Message-ID: <15465.29638.38617.927029@ns.bagley.org> (raw)
I would like to offer a small module I've written for benchmarking.
But I also have some questions, since I've never done this before.
A compressed tarball is here:
http://www.bagley.org/~doug/ocaml/benchmark/
This module is a fairly straight-forward port of the Perl Benchmark
module, which allows you to measure and compare the run-time of
functions. There is some ocamldoc style documentation included.
I have seen some other packages use autoconf, or custom makefiles,
sometimes with findlib (which I haven't really explored yet). Some
modules seem to install in /usr/local/lib/ocaml and some in +contrib.
I took the route of using Markus' fine OcamlMakefile, extending it with
some extra stuff for what I need. So, for example, it will install in
/usr/local/lib/ocaml/contrib by default, but you can override that by
defining an environment variable, as I briefly explain in the INSTALL
file. I honestly have no idea if what I've done will work on Windows, I
don't have an easy way of finding out right now.
Do people think that strategy is sufficient? Is there a best way to
package up a module for distribution? Would others like to see OCaml
offer a standard method of packaging, distributing, and building
modules? (It's becoming quite popular to offer this, for example,
Perl and Xemacs offer standard packaging systems). I believe I saw
one or more messages in the archives on this subject, so maybe it's
not just me.
Anyway, I would appreciate any feedback, whether it's about the
benchmark module, or issues of packaging a module. Thanks.
cheers,
doug
--
http://www.bagley.org/~doug/contact.shtml
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
reply other threads:[~2002-02-13 5:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15465.29638.38617.927029@ns.bagley.org \
--to=doug@bagley.org \
--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