caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Richard Jones <rich@annexia.org>
Cc: "O'Caml Mailing List" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml development site
Date: Fri, 07 May 2004 16:04:03 +0200	[thread overview]
Message-ID: <1083938642.12331.79.camel@ice.gerd-stolpmann.de> (raw)
In-Reply-To: <20040507115613.GA19412@redhat.com>

On Fre, 2004-05-07 at 13:56, Richard Jones wrote:
> On Fri, May 07, 2004 at 06:31:41AM -0500, John Goerzen wrote:
> > > * Are the services provided by these tools enough for you?  If not,
> > >   please be specific.
> > 
> > I'm not sure that a SourceForge derivative is really the right tool for
> > a CPAN alternative.  Those tools are more designed to facilitate
> > development of individual projects rather than to facilitate managing a
> > massive repository of related projects.
> 
> Yup, I think the idea is a little different from CPAN.  It's more like
> an alternative place to host projects which isn't Savannah (because of
> its well-publicised failures) or Sourceforge (depends on a company
> which may well go out of business).
> 
> Of course, a CPAN-like repository could also happen, but I guess it
> would have to be part of GODI now, with a way to upload source code as
> well.

I would be quite glad if it were not part of GODI. Hosting projects is
something different than hosting packages for a certain package manager.
And currently, GODI does not have the capacity to do all. I am also
convinced that the integrated CPAN way is not the right way for ocaml,
it is too complex for a non-scripting language.

Gerd
-- 
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany 
gerd@gerd-stolpmann.de          http://www.gerd-stolpmann.de
------------------------------------------------------------

-------------------
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:[~2004-05-07 14:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07 10:44 Christophe TROESTLER
2004-05-07 11:31 ` John Goerzen
2004-05-07 11:56   ` Richard Jones
2004-05-07 13:56     ` Olivier Grisel
2004-05-07 14:04     ` Gerd Stolpmann [this message]
2004-05-07 14:33     ` Christophe TROESTLER
2004-05-07 19:13   ` Evan Martin
2004-05-07 11:48 ` Nicolas Cannasse
2004-05-07 14:53   ` John Goerzen
2004-05-07 15:07     ` Nicolas Cannasse
2004-05-07 15:40       ` Richard Jones
2004-05-07 15:41         ` Richard Jones
2004-05-07 15:46     ` Gerd Stolpmann
2004-05-07 16:04   ` Paul Snively
2004-05-07 17:55 ` sylvain.le-gall
2004-05-07 18:09 ` N. Owen Gunden
2004-05-07 18:42   ` Benjamin Geer
2004-05-07 19:48     ` Christophe TROESTLER
2004-05-07 20:43 ` Kenneth Knowles
2004-05-08 10:06 ` Stefano Zacchiroli
2004-05-10  7:32 ` Jean-Christophe Filliatre

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=1083938642.12331.79.camel@ice.gerd-stolpmann.de \
    --to=info@gerd-stolpmann.de \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.org \
    /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).