From: Peter Brett <peter@peter-b.co.uk>
To: guile-devel@gnu.org
Subject: Re: summer of code project: cpan
Date: Tue, 29 Mar 2011 14:51:41 +0100 [thread overview]
Message-ID: <we1mk4fim3v6.fsf@ssclt001.eps.surrey.ac.uk> (raw)
In-Reply-To: m3hbazwcz9.fsf@unquote.localdomain
Andy Wingo <wingo@pobox.com> writes:
> Now that GNU is in the Google SoC, I'd like to propose again a CPAN for
> Guile. (It does needs a proper name, but that name doesn't have to
> correspond to the name of the command-line utility; see my other mail
> about "guido".)
>
> The proposal would be to start from dorodango, and to use stowfs
> locally. We keep (largely) the dorodango network interfaces, but the
> implementation exists in a Guile-specific project, with a non-dorodango
> name (so as not to conflict with Andreas's more portable project).
>
> Locally it uses something like stowfs and $XDG_DATA_DIRS, as noted in
> the previous SoC thread.
>
> The project can be developed outside of Guile initially, just
> integrating by defining "guido" commands. If everything works it can be
> integrated within Guile itself.
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/
Regards,
Peter
--
Peter Brett <peter@peter-b.co.uk>
Remote Sensing Research Group
Surrey Space Centre
next prev parent reply other threads:[~2011-03-29 13:51 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 [this message]
2011-03-29 14:16 ` Andy Wingo
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=we1mk4fim3v6.fsf@ssclt001.eps.surrey.ac.uk \
--to=peter@peter-b.co.uk \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).