Browse thread
[Caml-list] Dynamically evaluating OCaml code
-
John Goerzen
- Vitaly Lugovsky
- Samuel Mimram
-
Basile Starynkevitch
-
Issac Trotts
- Dustin Sallings
-
Brian Hurt
- Oleg Trott
- Ville-Pertti Keinonen
-
John Goerzen
-
Markus Mottl
-
Richard Jones
-
Markus Mottl
- Jon Harrop
-
John Goerzen
- Jean-Marc EBER
-
Trevor Andrade
-
Gerd Stolpmann
- skaller
-
John Goerzen
-
Gerd Stolpmann
-
Christophe TROESTLER
-
Gerd Stolpmann
-
Christophe TROESTLER
- Brandon J. Van Every
- John Goerzen
- Jacques GARRIGUE
-
Christophe TROESTLER
-
Gerd Stolpmann
-
Christophe TROESTLER
- Matt Gushee
-
Gerd Stolpmann
- Benjamin Geer
-
Gerd Stolpmann
- skaller
-
Markus Mottl
- John Goerzen
- Jon Harrop
-
Richard Jones
- Fernando Alegre
- Jean-Marc EBER
- Kenneth Knowles
- Brian Hurt
- skaller
-
Markus Mottl
- Issac Trotts
- Basile Starynkevitch
-
Issac Trotts
- clement capel
- Jon Harrop
- Walid Taha
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | skaller <skaller@u...> |
| Subject: | Re: [Caml-list] build tools - good vs. fast, both cheap |
On Fri, 2004-04-16 at 16:31, Brandon J. Van Every wrote: > So where are we? We're having the age old engineering argument, "good, > fast, cheap, pick any two." We're all open source developers so we're > all cheap. :-) We've got one camp that sees an all-OCaml build + > package management system as the goal. Count me in on that, and I will > label it the "GOOD AND CHEAP" camp. We've got another camp that sees > getting any build + package management system together as quickly as > possible from readily available parts as the goal. I will label it the > "FAST AND CHEAP" camp. Ok, then my opinion is that this analysis misses the point. We can do both. First hack together any crappy code that works, then make something elegant -- using the crappy code to help bootstrap the effort. How do we do this? Well, one thing must NOT be crappy, even for the crappy code -- and that is the specification. Writing a package manager isn't the problem, IMHO. The problem is defining what a package IS, where the pieces go, and how dependencies are stated.. etc etc. > What is the ultimate goal? I say, the ultimate goal is total ease of > use for an OCaml developer. NO! Ocaml developers don't need package managers, we're nerds, we'll happily use tarballs, CVS .. and even .. gasp .. autoconf.. :D Package managers are for our CLIENTS. I want to build something which USES your code, and be able to distribute MY code and not yours .. and know my client can get it easily .. preferably my build script will do that automatically in a uniform way for your code, fred's code, Joe's code and Mary's code .. -- John Skaller, mailto:skaller@users.sf.net voice: 061-2-9660-0850, snail: PO BOX 401 Glebe NSW 2037 Australia Checkout the Felix programming language http://felix.sf.net ------------------- 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