Hi!

[ I'm writing to this list (only), since I assume most R6RS Schemers are
  subscribed here. ]

I've now got dorodango (my R6RS package manager, see
<http://rotty.yi.org/software/dorodango/>) at the point where I'm
comfortable making a first release. Since it's been a while since I last
gave a report on dorodango's progress, here are some key features, which
are working at this point:

- Handling (multiple) package repositories, either HTTP or local file
  system ones

- Automatic dependency handling; dorodango will figure out which
  packages to install according to the (transitive) set of dependencies.

- A command-line interface exposing all the functionality.

- A manual that explains how to use it.

Please refer to the manual (linked from the URL above) for details.

What is completely missing from this manual is a "packaging guide",
i.e. how to package your own library collections. This involves just
adding a single, fairly short file (named pkg-list.scm) to the top-level
of you collection. There are several examples that can be followed if
people want to play with that part of dorodango. For example, I've
packaged the SRFI collection and Derick's xitomatl collection, and these
are the contents of their pkg-list.scm files:

(package (srfi (0))
  (libraries ((: "%3a" (* any)) -> "srfi")
             ("private" -> ("srfi" "private"))))

(package (xitomatl (0))
  (depends (srfi))
  (libraries 
   ("sxml-tools" -> ("xitomatl" "sxml-tools"))
   ("sxml-match" -> ("xitomatl" "sxml-match"))
   ("irregex" -> ("xitomatl" "irregex"))
   ("ssax" -> ("xitomatl" "ssax"))
   ("fmt" -> ("xitomatl" "fmt"))
   (sls -> "xitomatl")))

Writing documentation on how a pkg-list.scm file is structured is right
next up on my TODO list.

However, my main point here is that using dorodango, it is possible to
manage library collections more easily, and this enables us to follow a
more fine-grained approach: I propose to split libraries found in
several (personal) collections ATM out into their own packages. My list
so far is:

- SSAX (from xitomatl)
- sxml-tools (also from xitomatl)
- AS-match (xitomatl and spells)
- foof-loop (spells)
- irregex (xitomatl, spells)
- fmt (xitomatl, spells)
- parscheme (already packaged by me, but arcfide has a copy as well)

These, and more, are likely to be found in other collections as
well. Please identify further likely "packages". 

I'd also appreciate thoughts about how to _name_ the libraries inside
the collections. I think someone (Derick?) has mentioned using (ported
...) for third-party code ported to R6RS, and I'm fine with that, but
would like to hear other suggestions as well.

We also need to come up with a plan for how to manage these packages,
and in a sense assigning maintainer roles. I'd be willing to maintain at
least those that are currently in spells, but if someone else steps up
for one of those, that's OK with me as well.

Regards, Rotty
-- 
Andreas Rottmann -- <http://rotty.yi.org/>

Reply via email to