From: Ian Price <ianprice90@googlemail.com>
To: guile-devel@gnu.org
Cc: guile-user <guile-user@gnu.org>
Subject: guildhall packages
Date: Sun, 26 Aug 2012 02:01:44 +0100 [thread overview]
Message-ID: <87fw7aa2kn.fsf@Kagami.home> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 2512 bytes --]
Hello all,
As some of you are aware, I am in the process of packaging pieces of
software for a repository to be used with the guildhall package
manager for guile 2[0].
This is just a quick update on the progress of that, and a small
enticement to try to convince you to test it out[1]. Remember linus's
law, "given enough eyeballs all bugs are shallow" :P
Currently packaged is:
- fectors
Functional Vectors in Scheme
- bloom^[$B!]^[(Bfilter
Bloom Filter in Scheme
- clf
Common Log Format Parser
- wak
Wak is an r6rs porting project
- wak^[$B!]^[(Bprometheus
prototype-based message-passing object system
- wak^[$B!]^[(Bparscheme
parser combinator library
- wak^[$B!]^[(Bcommon
common infrastructure for the Wak ports
- wak^[$B!]^[(Btrc^[$B!]^[(Btesting
simple testing facility
- wak^[$B!]^[(Bsyn^[$B!]^[(Bparam
operators with extended parameter syntax
- wak^[$B!]^[(Birregex
portable regular expressions
- wak^[$B!]^[(Bfoof^[$B!]^[(Bloop
extensible looping library
- wak^[$B!]^[(Briastreams
lazy streams
- wak^[$B!]^[(Bssax
functional XML parsing framework
- wak^[$B!]^[(Bfmt
formatting combinator library
- pfds
Purely Functional Data Structures
- srfi
- sdom
An implementation of the W3C Dom in Scheme
- scss
A library for parsing, querying and emitting CSS
- guile^[$B!]^[(Blib
a down-scaled, limited-scope CPAN for Guile
- industria
G^[$(D+S^[(Bran Weinholt's library collection
(includes networking, crypot, text encoding, compression, bytevector
packing/unpackaing, and an amd64 disassembler)
With more to come!!
You can get more information on these libraries by doing, e.g.
$ guild show guile-lib
or install one with, e.g.
$ guild install guile-lib
So, that's the shameless plug, but I feel it is important we get used to
the idea that guile has a package manager, and that we should be using
it :).
If you think was a useful email, I can post a periodic update on new
packages and/or provide an atom feed for them. If not, I'll shut up :)
As mentioned previously, experimentation into a user upload facility is
ongoing, but if you want a library packaged/included shoot me a mail
(pure scheme only at the moment, hopefully scheme & c / elisp /
ecmascript / brainfuck soon)
0. https://github.com/ijp/guildhall/
1. Installation instructions -- https://gist.github.com/3327296
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next reply other threads:[~2012-08-26 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 1:01 Ian Price [this message]
2012-08-26 21:29 ` guildhall packages Ludovic Courtès
2012-08-26 21:34 ` Noah Lavine
2012-08-29 12:56 ` Ian Price
2012-08-29 13:25 ` cong gu
2012-08-29 16:42 ` Ian Price
2012-08-26 21:54 ` Julian Graham
2012-08-29 11:46 ` Ian Price
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=87fw7aa2kn.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=guile-devel@gnu.org \
--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).