From: "Till Varoquaux" <till.varoquaux@gmail.com>
To: caml-list@inria.fr
Cc: "Daniel de Rauglaudre" <daniel.de_rauglaudre@inria.fr>
Subject: Re: [Caml-list] Camlp4s 4.02 -> 4.03
Date: Tue, 10 Jul 2007 17:46:22 +0200 [thread overview]
Message-ID: <9d3ec8300707100846i32b2e429w6fa07413041d51df@mail.gmail.com> (raw)
In-Reply-To: <1184080656.14689.47.camel@rosella.wigram>
Another solution, if we want to stick with the possible collisions in
the names (which I personally very much dislike), would be to use a
small program (say "camlp4s-config" to stick with an old C tradition)
that would allow us to query for the naming informations. This would
be far from ideal but would at least allow for portable makefile.
Regards,
Till
On 7/10/07, skaller <skaller@users.sourceforge.net> wrote:
> On Tue, 2007-07-10 at 17:04 +0200, Daniel de Rauglaudre wrote:
>
> > For example:
> > ./configure -name camlp5
> >
> > would name the commands, files and manual pages: camlp5, camlp5o, camlp5r,
> > camlp5r.cma, camlp5.1 and so on, and the library would be installed in
> > a subdirectory camlp5 of the ocaml library directory.
>
> Due respect and all but this is really no good because it
> makes things WORSE than they already are. How can someone
> write a build script using camlp5 when it is called camlp4
> on another system ..?
>
> I think you should just fix the name to camlp5 or camlp4s,
> since you have the power to do that, and can't change INRIA's
> decision to retain the name camlp4 for an incompatible version.
>
> At least make the default camlp5 or camlp4s to support future
> co-existence.
>
> --
> John Skaller <skaller at users dot sf dot net>
> Felix, successor to C++: http://felix.sf.net
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
--
http://till-varoquaux.blogspot.com/
next prev parent reply other threads:[~2007-07-10 15:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 9:40 Camlp4s 4.02 Daniel de Rauglaudre
2007-07-09 9:58 ` [Caml-list] " Joel Reymont
2007-07-09 11:28 ` skaller
2007-07-10 8:33 ` Daniel de Rauglaudre
2007-07-10 9:08 ` skaller
2007-07-10 9:38 ` Olivier Andrieu
2007-07-10 13:19 ` Nicolas Pouillard
2007-07-10 11:13 ` Daniel de Rauglaudre
2007-07-10 13:05 ` skaller
2007-07-10 13:53 ` Daniel de Rauglaudre
2007-07-09 11:51 ` Richard Jones
2007-07-10 11:32 ` Stefano Zacchiroli
2007-07-10 12:19 ` Daniel de Rauglaudre
2007-07-10 12:33 ` Stefano Zacchiroli
2007-07-10 15:04 ` [Caml-list] Camlp4s 4.02 -> 4.03 Daniel de Rauglaudre
2007-07-10 15:08 ` Stefano Zacchiroli
2007-07-10 22:39 ` Markus E.L.
2007-07-10 23:30 ` [Caml-list] camlp4..camlp5 Daniel de Rauglaudre
2007-07-11 6:45 ` Stefano Zacchiroli
2007-07-11 10:54 ` Markus E.L.
2007-07-11 16:11 ` Daniel de Rauglaudre
2007-07-11 10:52 ` Markus E.L.
2007-07-11 7:52 ` [Caml-list] Camlp4s 4.02 -> 4.03 Nicolas Pouillard
2007-07-10 15:17 ` skaller
2007-07-10 15:46 ` Till Varoquaux [this message]
2007-07-10 15:58 ` skaller
2007-07-10 16:08 ` Till Varoquaux
2007-07-10 16:46 ` skaller
2007-07-10 13:12 ` [Caml-list] Camlp4s 4.02 skaller
2007-07-10 13:54 ` Daniel de Rauglaudre
2007-07-10 14:40 ` Yitzhak Mandelbaum
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=9d3ec8300707100846i32b2e429w6fa07413041d51df@mail.gmail.com \
--to=till.varoquaux@gmail.com \
--cc=caml-list@inria.fr \
--cc=daniel.de_rauglaudre@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