guildhall packages

guildhall packages

[Ian Price]

[-- 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"

Re: guildhall packages

[Ludovic Courtès]

Hi Ian!

Ian Price <ianprice90@googlemail.com> skribis:

> 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:

Woow, excellent work!  FWIW, I was able to “guild update”, “guild show”,
and “guild install pfds”.

> 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 :)

I like the updates, keep up the good work!  :-)

> 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)

Nice.  Any plan for Scheme & C?  (Guix?  hint, hint. ;-))

What about test suites, docs, and non trivial build systems in general?

Thanks,
Ludo’.

Re: guildhall packages

[Noah Lavine]

Hello,

On Sun, Aug 26, 2012 at 5:29 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Ian Price <ianprice90@googlemail.com> skribis:
>> 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 :)
>
> I like the updates, keep up the good work!  :-)

I also appreciate the messages and the hard work. Thank you!

Noah

Re: guildhall packages

[Ian Price]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 2102 bytes --]

ludo@gnu.org (Ludovic Court^[$(D+2^[(Bs) writes:

> Woow, excellent work!  FWIW, I was able to ^[$B!H^[(Bguild update^[$B!I^[(B, ^[$B!H^[(Bguild show^[$B!I^[(B,
> and ^[$B!H^[(Bguild install pfds^[$B!I^[(B.
Great
>> 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)
>
> Nice.  Any plan for Scheme & C?  (Guix?  hint, hint. ;-))
Scheme & C is obviously a huge part of guile, and so it's important that
gets done. There is some support for "installation hooks" that would be
used for this, though there is no documentation at present. I will try
and get some examples prepared for it.

> What about test suites, docs, and non trivial build systems in general?

As for documentation, it's the same deal (almost). Guildhall currently
recognises four "categories" of file. libraries, programs[1],
documentation, and man, and each of these gets stored in a different
place in the users .local[0] directory corresponding to normal unix
conventions.

libraries in ~/.local/share/guile/site/2.0
programs  in ~/.local/share/guildhall/2.0/$name/programs [2]
documentation in ~/.local/share/doc/guildhall/2.0/$name
man in prefix/share/man/man-$section/

Some files are automatically picked up as documenation, and placed in
the appropriate directory: README, COPYING, NEWS, etc.

For more complicated documentation, building info pages etc, I think you
would need to create an installation hook for this ATM, but for some
common formats it would be a useful feature to add to guildhall itself.

0. the prefix is configurable, but this will do for expository purposes
1. guildhall seems to make some sort of a distinction between "programs"
and "executables", but I'm not sure what the reasoning is for this.
2. executables would go in ~/.local/share/guildhall/2.0/$name/bin

-- 
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"

Re: guildhall packages

[cong gu]

Hi,

In guildhall, I can use other packages, but there are two problems
with package 'srfi'.
The first is I have to add 'sls' to %load-extensions. This is easy.
The second is that the filenames seem not compatible with guile's
module searching.
For example it is 'srfi/%3a41.sls' instead of guile's way like
'srfi/srfi-41.sls'

scheme@(guile-user)> (use-modules (srfi srfi-41))
While compiling expression:
ERROR: no code for module (srfi srfi-41)

How to make them work?

--
Cong Gu

Re: guildhall packages

[Ian Price]

cong gu <gucong43216@gmail.com> writes:

> scheme@(guile-user)> (use-modules (srfi srfi-41))
> While compiling expression:
> ERROR: no code for module (srfi srfi-41)

This was a mistake on my part, and I mentioned it on guile-devel a few
days ago. I will need to upload a new package.


-- 
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"

Re: guildhall packages

[Julian Graham]

Hi Ian,


On Sat, Aug 25, 2012 at 9:01 PM, Ian Price <ianprice90@googlemail.com> wrote:
> Currently packaged is:
> ...

Wow, that's a big list! Thanks in particular for packaging my stuff
(scss and sdom). Is there any information that library authors need to
have in order to make it easy for their work to be included in
guildhall?


> If you think was a useful email, I can post a periodic update on new
> packages and/or provide an atom feed for them.

Yes please! Thanks doing this work!


Regards,
Julian

Re: guildhall packages

[Ian Price]

Julian Graham <joolean@gmail.com> writes:

> Wow, that's a big list! Thanks in particular for packaging my stuff
> (scss and sdom). Is there any information that library authors need to
> have in order to make it easy for their work to be included in
> guildhall?

As it stands, it is pretty easy. All that is necessary is a pkg-list.scm
file that specifies how the files are to be installed. The format is
pretty simple, and can be copied from an existing one, and there is also
a grammar in the manual.

Other than that, send me an email and I'll include it. User-submitted
uploads not available yet, though it is a priority concern. 

-- 
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"