From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: summer of code ideas
Date: Mon, 7 Mar 2011 15:40:12 -0500 [thread overview]
Message-ID: <AANLkTikFJeqXvZhEf8cPuRAaZVF9Gt2jSS3mkSaw3mDE@mail.gmail.com> (raw)
In-Reply-To: <m3tyfeaevu.fsf@unquote.localdomain>
Also, about your CPAN for guile (CGAN?) idea - it seems like with what
you said about stowfs that what you're looking for is similar to Nix,
but used to install Guile packages. (www.nixos.org)
Do you think it would be useful to just compile a version of Nix with
a different root directory, make some Guile bindings, and use that?
Noah
On Mon, Mar 7, 2011 at 2:51 PM, Andy Wingo <wingo@pobox.com> wrote:
> Hey all,
>
> We need to get together a few Guile-proposed projects for SoC students
> to hack on. How about we collect them here in this thread. I'll kick
> it off with one idea:
>
> * A CPAN for Guile. My initial thoughts are that you want a
> combination of APT-like discovery and download of sources of
> software, and a stowfs-like local storage, allowing you to update a
> tree of symlinks in $XDG_DATA_DIRS/guile/2.0/ to add packages, roll
> back changes, etc. See
> http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
> for more on $XDG_DATA_DIRS.
>
> C extensions are outside the scope of this project. IMO a CPAN for
> Guile should not compile C helper libraries.
>
> You can start here by doing a survey of what other schemes do:
> chicken and racket being the obvious ones, and also perhaps taking a
> look at cabal and other CPAN-alikes developed in the last 10 years.
>
> You'd need to define a format for code -- tarballs or something.
> You need to think about signing too, and the possibility both of
> dumb servers and smart servers. You'll need to write a web client
> in Guile, if one hasn't been written yet. In short, a large project
> for an ambitious and careful hacker!
>
> Regards,
>
> Andy
> --
> http://wingolog.org/
>
>
next prev parent reply other threads:[~2011-03-07 20:40 UTC|newest]
Thread overview: 17+ 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
2011-03-07 20:40 ` Noah Lavine [this message]
2011-03-07 20:46 ` summer of code ideas Andy Wingo
2011-03-07 21:27 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2011-03-07 20:23 Mike Gran
2011-03-07 21:25 ` Jose A. Ortega Ruiz
2011-03-08 1:10 ` Mark H Weaver
2011-03-08 1:45 Mike Gran
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=AANLkTikFJeqXvZhEf8cPuRAaZVF9Gt2jSS3mkSaw3mDE@mail.gmail.com \
--to=noah.b.lavine@gmail.com \
--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).