From: carl hansen <carlhansen1234@gmail.com>
To: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Yet another GNU Guile package manager (Fwd: Re: How to make GNU Guile more successful)
Date: Thu, 16 Mar 2017 02:03:02 -0700 [thread overview]
Message-ID: <CAHEkXCRmd=e2bWM1dVwiNjZNvztczzzG7BmuVjW+B8ik2xP49A@mail.gmail.com> (raw)
In-Reply-To: <179cbaf2-6327-2b1b-c963-44bb0902fb0d@hypermove.net>
FYI:
"
guile-lib
guile-lib is intended as an accumulation place for pure-scheme Guile
modules, allowing for people to cooperate integrating their generic Guile
modules into a coherent library. Think "a down-scaled, limited-scope CPAN
<http://www.cpan.org/> for Guile".
Also, it can be seen as a code staging area for Guile; the Guile developers
could decide to integrate some of the code into guile-core. An example for
a possible candidate is SRFI-35."
http://www.nongnu.org/guile-lib/
next prev parent reply other threads:[~2017-03-16 9:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 2:08 How to make GNU Guile more successful Vítor De Araújo
2017-03-10 9:55 ` Arne Babenhauserheide
2017-03-10 10:03 ` Panicz Maciej Godek
2017-03-10 14:27 ` vbuaraujo
2017-03-10 15:08 ` Panicz Maciej Godek
2017-03-11 7:19 ` Thien-Thi Nguyen
2017-03-13 15:55 ` Nala Ginrut
2017-03-13 16:14 ` Panicz Maciej Godek
2017-03-10 20:17 ` Amirouche
2017-03-10 20:27 ` Yet another GNU Guile package manager (Fwd: Re: How to make GNU Guile more successful) Amirouche
2017-03-11 1:56 ` Nala Ginrut
2017-03-11 16:49 ` Amirouche
2017-03-16 9:03 ` carl hansen [this message]
2017-03-16 12:07 ` Matt Wette
2017-03-16 21:15 ` Alex Kost
2017-03-11 0:50 ` How to make GNU Guile more successful Vítor De Araújo
2017-03-11 3:02 ` Vítor De Araújo
2017-03-11 7:42 ` Thien-Thi Nguyen
2017-03-14 3:26 ` Christopher Allan Webber
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='CAHEkXCRmd=e2bWM1dVwiNjZNvztczzzG7BmuVjW+B8ik2xP49A@mail.gmail.com' \
--to=carlhansen1234@gmail.com \
--cc=guile-user@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).