From: Richard Jones <rich@annexia.org>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Camlp5 release 5.03
Date: Wed, 21 Nov 2007 19:10:07 +0000 [thread overview]
Message-ID: <20071121191006.GA31390@furbychan.cocan.org> (raw)
In-Reply-To: <200711211801.08746.jon@ffconsultancy.com>
On Wed, Nov 21, 2007 at 06:01:08PM +0000, Jon Harrop wrote:
> On Wednesday 21 November 2007 17:19, Richard Jones wrote:
> > Debian ships both. Fedora will soon as well.
>
> So package maintainers are already forking the OCaml distribution into
> separate parts?
I guess it depends what you mean by "forking", but it's standard
practice, in all areas not just OCaml, for a single source package
(eg. ocaml-3.10.0.tar.gz) to generate many different binary packages
(eg. ocamlc, ocamlopt, ocamldoc, camlp4, labltk, etc.)
This means that you can install just the bits you need, and
furthermore that another package only needs to depend upon the parts
it actually uses -- this saves disk space & network bandwidth!
The camlp5 package installs in $OCAMLLIBDIR/camlp5 so it doesn't
conflict with camlp4 from the base OCaml package, with an appropriate
findlib META file. You need to make some adjustments to your Makefile
but those are usually very minor compared to rejigging your source to
be compatible with the new camlp4.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2007-11-21 19:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 9:52 Daniel de Rauglaudre
2007-11-20 11:33 ` [Caml-list] " David Teller
2007-11-20 12:47 ` Daniel de Rauglaudre
2007-11-21 17:19 ` Richard Jones
2007-11-21 18:01 ` Jon Harrop
2007-11-21 19:10 ` Richard Jones [this message]
2007-11-21 20:10 ` Jon Harrop
2007-11-21 21:12 ` Richard Jones
2007-11-22 9:42 ` Stefano Zacchiroli
2007-11-21 19:13 ` Pietro Abate
2007-11-22 9:37 ` Stefano Zacchiroli
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=20071121191006.GA31390@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
/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