caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Richard Jones <rich@annexia.org>
To: BdB <benoit.de-boursetty+caml-list@m4x.org>
Cc: Issac Trotts <ijtrotts@ucdavis.edu>, caml-list@inria.fr
Subject: Re: [Caml-list] CTAN/CPAN for Caml (COCAN ...?)
Date: Wed, 16 Jul 2003 10:22:48 +0100	[thread overview]
Message-ID: <20030716092248.GA8914@redhat.com> (raw)
In-Reply-To: <KMEFLMEIPOIDHNANKEIJAEBACAAA.benoit.de-boursetty+caml-list@m4x.org>

On Wed, Jul 16, 2003 at 08:43:20AM +0200, BdB wrote:
> ?.02 here: there's a couple of stuff that a CPAN-like website could do
>   1) hosting libs
>   2) cross-referencing & automatic dependency generation
>   3) registry (the business of ensuring non-collision)

Another important point would be:

4) A standard packaging and build process.

For example, you can download any Perl package and type:

	perl Makefile.PL && make && sudo make install

You can use Perl's CPAN module to download, compile and install the
dependent packages with one command. It all works automatically
because all Perl packages follow a few fairly simple rules.

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

I agree this is a problem, but a Java-like module namespace is about
the worst possible solution. Perl has many thousands of packages but
does not require it. Mostly this is because of an informal honour
system: no one names their package "CGI" unless it is absolutely the
best system for writing CGI scripts. Little-used or still-born
packages can also be kicked out of the archive.

Rich.

-- 
Richard Jones. http://www.annexia.org/ http://freshmeat.net/users/rwmj
Merjis Ltd. http://www.merjis.com/ - all your business data are belong to you.
PTHRLIB is a library for writing small, efficient and fast servers in C.
HTTP, CGI, DBI, lightweight threads: http://www.annexia.org/freeware/pthrlib/

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


  parent reply	other threads:[~2003-07-16  9:23 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
2003-07-16  9:22         ` Richard Jones [this message]
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=20030716092248.GA8914@redhat.com \
    --to=rich@annexia.org \
    --cc=benoit.de-boursetty+caml-list@m4x.org \
    --cc=caml-list@inria.fr \
    --cc=ijtrotts@ucdavis.edu \
    /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;
as well as URLs for NNTP newsgroup(s).