From: Andreas Rottmann <a.rottmann@gmx.at>
To: Paul Raccuglia <praccugl@haverford.edu>
Cc: guile-devel@gnu.org
Subject: Re: Hi! Interested in GSoC. Feedback on these ideas?
Date: Thu, 07 Apr 2011 12:43:02 +0200 [thread overview]
Message-ID: <871v1egx55.fsf@gmx.at> (raw)
In-Reply-To: <BANLkTimxCQceZV=2mPpcuqwdTnwMi1tvaA@mail.gmail.com> (Paul Raccuglia's message of "Wed, 6 Apr 2011 20:40:15 -0400")
Paul Raccuglia <praccugl@haverford.edu> writes:
> Hi! I'm interested in working on guile as part of the Google Summer of Code.
>
[...]
> Currently I am thinking about:
>
> - A package manager (in the vein of apt-get)
> I know this is one that's come up a bit. I was thinking of writing a
> small web interface to browse packages, an aptitude style command-line
> method for downloading, verifying the hashes, checking dependencies,
> and then install the package(s) and an uninstall function as well. I
> saw the proposal of working with dorodango; I might look at it, but
> from what I saw of the code base, I thought it would make sense to try
> to write a GUILE specific package-manager.
>
Could you be more specific? What exactly in the code base did make you
think so?
Thanks, Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
next prev parent reply other threads:[~2011-04-07 10:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 0:40 Hi! Interested in GSoC. Feedback on these ideas? Paul Raccuglia
2011-04-07 3:36 ` nalaginrut
2011-04-07 8:31 ` Mark H Weaver
2011-04-07 13:10 ` Noah Lavine
2011-04-07 14:12 ` nalaginrut
2011-04-07 14:25 ` Problem with GCC as a Scheme compiler: tail calls Mark H Weaver
2011-04-07 14:37 ` Noah Lavine
2011-04-11 22:31 ` Andy Wingo
2011-04-11 23:12 ` Noah Lavine
2011-04-07 10:43 ` Andreas Rottmann [this message]
2011-04-07 13:21 ` Hi! Interested in GSoC. Feedback on these ideas? Paul Raccuglia
2011-04-07 21:45 ` Paul Raccuglia
2011-04-08 0:01 ` Paul Raccuglia
2011-04-08 1:00 ` dsmich
2011-04-08 4:36 ` Paul Raccuglia
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=871v1egx55.fsf@gmx.at \
--to=a.rottmann@gmx.at \
--cc=guile-devel@gnu.org \
--cc=praccugl@haverford.edu \
/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).