From: Andreas Rottmann <a.rottmann@gmx.at>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: CPAN for Guile
Date: Tue, 29 Mar 2011 01:03:25 +0200 [thread overview]
Message-ID: <878vvyn8zm.fsf@gmx.at> (raw)
In-Reply-To: <m3lj0qab4s.fsf@unquote.localdomain> (Andy Wingo's message of "Mon, 07 Mar 2011 22:12:03 +0100")
Andy Wingo <wingo@pobox.com> writes:
> On Mon 07 Mar 2011 21:13, Andreas Rottmann <a.rottmann@gmx.at> writes:
>
>> I'm (very slowly) working on getting dorodango[0] to work on Guile. In
>> principle, nothing in Dorodango is inherently tied to R6RS -- it should
>> very reasonably be possible to use it for Guile-specific packages as
>> well.
>>
>> [0] http://home.gna.org/dorodango/
>
> Looks very nice, and well thought-out. Dorodango would be an excellent
> starting point.
>
> Alaric Snell-Pym gave us an overview of Chicken's system here:
> http://rotty.yi.org/irclogs/freenode/#guile/2011-02-10/#e212
>
> I agree with him that one of the most important aspects about
> CPAN-alikes is the social one: how the system enables the hack, and with
> what flavor. For example right now Guile has a tight center, enforced
> by the stability needs of Guile, as well as the copyright assignment
> policy, then a wide-orbiting set of comet- and asteroid-like libraries.
> A good CPAN-alike would smooth this out into a gradient of more and less
> experimental hacks, to enable participation of folks with useful
> libraries, but which don't need to be in Guile proper.
>
> It would be good to also think about modules' test suites,
> documentation, code coverage, code analysis and such, and be opinionated
> about that.
>
Yeah, that are all areas I envisioned for dorodango, but have not yet
tackled.
> It would be interesting to have the ability to add on, as an additional
> source of code, repos with portable R6RS code.
>
Indeed. Dorodango already has the capability to deal with multiple
repositories, and a Guile-specific version of Dorodango would probably
come with a default configuration that points to Guile's (default)
reprository; users would then add additional ones according to their
likes.
> I wonder how this would affect us socially though.
>
No idea :-).
Regards, Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
next prev parent reply other threads:[~2011-03-28 23:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 19:51 summer of code ideas Andy Wingo
2011-03-07 20:12 ` Noah Lavine
2011-03-07 21:33 ` Ludovic Courtès
2011-03-07 22:11 ` Noah Lavine
2011-03-07 22:27 ` Ludovic Courtès
2011-03-07 22:37 ` Noah Lavine
2011-03-08 13:00 ` Ludovic Courtès
2011-03-07 20:13 ` CPAN for Guile Andreas Rottmann
2011-03-07 21:12 ` Andy Wingo
2011-03-28 23:03 ` Andreas Rottmann [this message]
2011-03-07 20:40 ` summer of code ideas Noah Lavine
2011-03-07 20:46 ` Andy Wingo
2011-03-07 21:27 ` Ludovic Courtès
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=878vvyn8zm.fsf@gmx.at \
--to=a.rottmann@gmx.at \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).