Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Wolfgang Müller" <Wolfgang.Mueller2@uni-bayreuth.de>
To: "BdB" <benoit.de-boursetty+caml-list@m4x.org>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] CTAN/CPAN for Caml (COCAN ...?)
Date: Wed, 16 Jul 2003 09:07:40 +0200	[thread overview]
Message-ID: <200307160907.40563.wolfgang.mueller2@uni-bayreuth.de> (raw)
In-Reply-To: <KMEFLMEIPOIDHNANKEIJAEBACAAA.benoit.de-boursetty+caml-list@m4x.org>

On Wednesday 16 July 2003 08:43, BdB wrote:
> €.02 here: there's a couple of stuff that a CPAN-like website could do
My $0.02 (for character table reasons ;-) )
>   1) hosting libs
>   2) cross-referencing & automatic dependency generation
>   3) registry (the business of ensuring non-collision)
>
> It seems to me that the sites you mention only provide hosting among these
> three points. Which is still interesting.

I agree completely here. I think it would be great to have some automatic 
installation or downloading facility like the CPAN module in perl. I think 
like this it would be easier to make people like me (i.e. newbies) look for 
useful stuff before starting to code, and make it easy for people to ship 
their code if it needs to be shipped. 

Personally, in my experience with CPAN IMHO what is needed most for shipping 
code is some code that generates a tarball of all the prerequisites needed 
for a given package of code, together with an idiot-proof makefile. Most 
people I work with do not like the -MCPAN (it can make problems if you're not 
root, you have to answer many questions, there are firewalls), so I cannot 
send them simple scripts that use the CPAN module for downloading the useful 
stuff, I have to do the actual tarballs myself.

> I would think that coding 2) is just a matter of motivation. ocamldep and
> camlp4 should help.

Oh, for this I am too newbyish

> As for the last point... well, one possible drawback of current O'CaML is
> its module namespace. My fear is that module names are soon enough going to
> look like JoesXMLParser to distinguish it from MikesXMLParser (betting on
> the success of the initiative here). Well, actually there can be modules
> within modules, so that's not exactly a flat module namespace. But if
> someone makes a module called Joe.XMLParser, it has got to be defined in
> joe.ml[i], which is in my opinion a pretty bad name to give to a file
> containing an XML parser. Maybe java-like module namespace partition is
> something worth considering for efficient community management?

...sounds great to a newbie like me...

Cheers,
Wolfgang

-------------------
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


  reply	other threads:[~2003-07-16  7:07 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 18:09 Richard Jones
2003-07-15 18:37 ` Erik Arneson
2003-07-18  8:08   ` John Max Skaller
2003-07-16  3:13 ` BdB
2003-07-16  3:22   ` Alexander V. Voinov
2003-07-16  5:53     ` Issac Trotts
2003-07-16  6:43       ` BdB
2003-07-16  7:07         ` Wolfgang Müller [this message]
2003-07-16  9:22         ` Richard Jones
2003-07-16  9:51           ` Wolfgang Müller
2003-07-17  8:42         ` Florian Hars
2003-07-16  6:52   ` Florian Hars
2003-07-18  8:14 ` John Max Skaller
2003-07-18  8:42   ` Richard Jones
2003-07-18 15:46     ` Stefano Zacchiroli
2003-07-18 20:49       ` Yamagata Yoriyuki
2003-07-19 11:25         ` Daniel Bünzli
2003-07-19 19:47           ` Yamagata Yoriyuki
2003-07-18 14:29   ` Shawn Wagner
2003-07-19 11:55     ` [Caml-list] GODI (was: CTAN/CPAN for Caml (COCAN ...?)) Gerd Stolpmann
2003-07-19 12:18       ` Fernando Alegre
2003-07-19 12:38         ` Gerd Stolpmann
2003-07-19 13:20           ` Fernando Alegre
2003-07-19 22:58             ` Kip Macy
2003-07-19 20:05           ` [Caml-list] GODI Yamagata Yoriyuki
2003-07-19 20:40           ` [Caml-list] GODI (was: CTAN/CPAN for Caml (COCAN ...?)) BdB
2003-07-20  9:55             ` Gerd Stolpmann
2003-07-20 18:30               ` Christian Lindig
2003-07-21 16:19                 ` james woodyatt
2003-07-21 16:32                   ` Richard Jones
2003-07-21 16:37                     ` Richard Jones
2003-07-21 20:37                     ` james woodyatt
2003-07-21 21:48                     ` BdB
2003-07-22 20:48                   ` Christian Lindig
2003-07-22  0:01                 ` BdB
2003-07-22  2:35                   ` [Caml-list] licensing (was Re: GODI (was: CTAN/CPAN for Caml (COCAN ...?))) Alan Post
2003-07-22  7:57                     ` Dominique Quatravaux
2003-07-22  8:02                     ` BdB
2003-07-22 15:29                   ` [Caml-list] GODI Yamagata Yoriyuki
2003-07-20 23:11               ` Yamagata Yoriyuki
2003-07-21 12:01                 ` Fernando Alegre
2003-07-23  9:35       ` [Caml-list] GODI (was: CTAN/CPAN for Caml (COCAN ...?)) Xavier Leroy
2003-07-23 13:20         ` Gerd Stolpmann
2003-07-24 16:34           ` Eray Ozkural
2003-07-23 17:56         ` David Brown
2003-07-23 18:36           ` Fernando Alegre

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=200307160907.40563.wolfgang.mueller2@uni-bayreuth.de \
    --to=wolfgang.mueller2@uni-bayreuth.de \
    --cc=benoit.de-boursetty+caml-list@m4x.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