From: Andy Wingo <wingo@pobox.com>
To: Peter Brett <peter@peter-b.co.uk>
Cc: guile-devel@gnu.org
Subject: Re: summer of code project: cpan
Date: Tue, 29 Mar 2011 16:16:26 +0200 [thread overview]
Message-ID: <m3oc4u6mh1.fsf@unquote.localdomain> (raw)
In-Reply-To: <we1mk4fim3v6.fsf@ssclt001.eps.surrey.ac.uk> (Peter Brett's message of "Tue, 29 Mar 2011 14:51:41 +0100")
On Tue 29 Mar 2011 15:51, Peter Brett <peter@peter-b.co.uk> writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> Now that GNU is in the Google SoC, I'd like to propose again a CPAN for
>> Guile.
>
> I urge caution. This sounds suspiciously similar to Ruby "gems", which
> have worked okay for developers but have caused massive problems for
> system administrators, end users and distributions.
>
> This article on LWN is a good read (although it contains some unrelated
> criticism of other aspects of Ruby development).
>
> http://lwn.net/Articles/423732/
Valid points, all. I think the thing to do is to make it easy to
package Guile modules, as stored and versioned in our CPAN, as native
packages. People who want to use native packages can do that. The
repository can have an idea of what's installed on the system, and
what's installed by the user. Guile developers can easily publish and
distribute code via the CPAN, just as Perl developers do.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-03-29 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 11:45 summer of code project: cpan Andy Wingo
2011-03-28 23:46 ` Andreas Rottmann
2011-03-29 13:51 ` Peter Brett
2011-03-29 14:16 ` Andy Wingo [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3oc4u6mh1.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=peter@peter-b.co.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).