From: Alain.Frisch@ens.fr
To: Benjamin Geer <ben@socialtools.net>
Cc: Caml list <caml-list@inria.fr>
Subject: Re: [Caml-list] GODI news
Date: Wed, 3 Dec 2003 00:51:59 +0100 (MET) [thread overview]
Message-ID: <Pine.SOL.4.44.0312030040300.12647-100000@clipper.ens.fr> (raw)
In-Reply-To: <3FCD21F9.9010100@socialtools.net>
On Tue, 2 Dec 2003, Benjamin Geer wrote:
> I'd love to, but I can't find a document that explains how to do that.
> I've read the README.devel, but it's not clear to me which parts of it
> are talking about the development of GODI itself, and which parts are
> explaining how to make a GODI package. There's a section called 'What
> to put in the Makefile' that looks relevant, but I'm wondering: Which
> Makefile? What do I need besides a Makefile?
Of course, Gerd will be able to provide a better answer himself, but here
is what I learnt.
You're responsible for the whole build directory except the work/
subdirectory (cf "The build directory in detail" in README.devel). AFAIK,
all the information in README.devel are relevant to make a GODI package (I
cannot see anything about the developement of GODI itself in this file).
I suggest to start from an existing package of the "same shape". For
instance, if you want to package a library which is a binding to a C
library which may need to be installed, you can start from the pcre
packages (conf-pcre, base-pcre, godi-pcre). If the library is pure OCaml,
you can start from godi-pxp. If the library needs the OCaml sources,
start from godi-wlex.
You'll need to do "bmake makesums" in you fresh build directory to
generate checksums for the files to be downloaded.
You can test your new package with godi_console by adding a line to the
file available.current, before sending the .tgz file to Gerd.
-- Alain
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-12-02 23:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 22:35 Gerd Stolpmann
2003-12-02 23:09 ` Alain.Frisch
2003-12-02 23:36 ` Benjamin Geer
2003-12-02 23:51 ` Alain.Frisch [this message]
2003-12-03 5:12 ` William Lovas
2003-12-03 11:16 ` Sven Luther
2003-12-04 4:25 ` William Lovas
2003-12-08 12:44 ` Sven Luther
2003-12-03 21:14 ` Sylvain LE GALL
2003-12-03 23:59 ` Gerd Stolpmann
2003-12-04 0:41 ` Benjamin Geer
2003-12-05 21:23 ` Gerd Stolpmann
2003-12-03 7:49 ` Byron Hale
-- strict thread matches above, loose matches on Subject: below --
2012-10-22 2:39 Gerd Stolpmann
2004-05-14 16:29 Gerd Stolpmann
2004-04-28 12:38 Gerd Stolpmann
2004-02-27 9:41 Gerd Stolpmann
2004-01-04 21:12 Gerd Stolpmann
2003-11-05 21:28 [Caml-list] GODI News Gerd Stolpmann
2003-11-05 22:59 ` Ken Rose
2003-08-08 21:20 [Caml-list] GODI news Gerd Stolpmann
2003-08-08 21:37 ` Matt Gushee
2003-08-09 9:04 ` Gerd Stolpmann
2003-08-09 17:05 ` Matt Gushee
2003-08-09 18:06 ` Dmitry Bely
2003-08-09 18:44 ` Alexander V. Voinov
2003-08-09 21:16 ` Sven Luther
2003-08-10 1:11 ` skaller
2003-08-10 7:35 ` Sven Luther
2003-08-10 20:25 ` skaller
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=Pine.SOL.4.44.0312030040300.12647-100000@clipper.ens.fr \
--to=alain.frisch@ens.fr \
--cc=ben@socialtools.net \
--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