Gnus development mailing list
 help / color / mirror / Atom feed
From: jzawodn@wcnet.org (Jeremy D. Zawodny)
Cc: dave@bfnet.com, ding@gnus.org
Subject: Re: OFFTOPIC:  Where do you get your elisp?
Date: 03 Aug 1999 21:24:41 -0400	[thread overview]
Message-ID: <m3btcocp7q.fsf@peach.z.org> (raw)
In-Reply-To: "Edward J. Sabol"'s message of "Tue, 3 Aug 1999 15:36:10 -0400 (EDT)"

"Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov> writes:

> I think the current state of elisp archiving is pretty sad. The elisp user
> *and* developer communities badly need the equivalent of Perl's impressive
> Comprehensive Perl Archive Network (or CPAN). 

[snip]

> Unfortunately, I don't have the time or resources to fix it.

Hm. I may have a bit of free time on my hands... I might be able to
offer the services of a machine and some of my time to build a
browsable archive. (I've suffered the pains of unsuccessfully trying to
find a few lisp packages too many times. DejaNews is good, but not
always the best way to do it.)

I just don't know which would be more appropriate:

 (1) An index-only approach (like www.freshmeat.net)

or

 (2) Something like CPAN (distributed copies of the actual code)

Advantages and disadvantages either way. Maybe a hybrid. Maybe we
could just try and convince would-be Lisp hackers to use Freshmeat? Or
do to many people not have a place where they can put their code (http
or ftp server).

Hm.

Ideas?

Jeremy
-- 
Jeremy D. Zawodny                Web Geek, Perl Hacker, etc.
http://www.wcnet.org/~jzawodn/   jzawodn@wcnet.org

  9:20pm  up 19 days, 21:22,  6 users,  load average: 0.05, 0.09, 0.08



  parent reply	other threads:[~1999-08-04  1:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-03 18:56 dave
1999-08-03 19:13 ` William M. Perry
1999-08-03 19:23   ` dave
1999-08-03 19:42     ` William M. Perry
1999-08-06  3:26       ` Greg Stark
1999-09-24 17:17         ` Lars Magne Ingebrigtsen
1999-08-03 19:28 ` Bill White
1999-08-03 19:36 ` Edward J. Sabol
1999-08-03 20:05   ` Bruce Stephens
1999-08-04  1:24   ` Jeremy D. Zawodny [this message]
1999-08-04  8:05     ` Kai Großjohann
     [not found]     ` <wtnoggoorr6.fsf@licia.dtek.chalmers.se>
1999-08-04 10:37       ` luis fernandes
1999-08-04 11:45         ` Felix Lee
1999-08-04 14:55         ` Edward J. Sabol
1999-08-04 16:13           ` Arcady Genkin
1999-08-05 13:50             ` Florian Weimer
1999-08-04 14:40       ` Randal L. Schwartz
1999-08-04 16:28         ` William M. Perry
1999-09-24 17:20     ` Lars Magne Ingebrigtsen
1999-08-04  9:05 ` Eric Marsden
1999-08-04 16:48   ` Colin Marquardt

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=m3btcocp7q.fsf@peach.z.org \
    --to=jzawodn@wcnet.org \
    --cc=dave@bfnet.com \
    --cc=ding@gnus.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).