Re: xguile and guile-xlib

[thi <ttn at revel dot glug dot org>]

now that i've had a chance to get guile-projects page relatively stable,
i'll be working on setting up a guile modules repo (perhaps named "GUMM"
for "guile user module mix" -- naming suggestions welcome!).  the aim of
this repo will be not only aggregation (which any fool can set up), but
also characterization (which this fool finds interesting).  that is,
each piece of code interned will be analyzed to mine out info such as:

	- system dependencies (guile version, system)
	- module-level dependencies
	- supplied interface
	- interface changes (versioning)
	- global state
	- [your favorite charaterization(s) here]

this is in addition to placing the code in a specific hierarchy (which
we have beaten to death here -- newbies: you can grep the archives for
"module" and "hierarchy").

from a user point of view, we should develop a client akin to lispdir.el
that groks these characterizations and can do the right thing.  (please
help me define what the right thing is.)

the next step in attaining true snarfiency would be to apply the
characterization to code not specifically written for guile, e.g.,
r*rs-clean code at schemers.org and swig-wrapped libraries from
/usr/local/lib, etc...

as for xguile vs guile-xlib, unification would be cool, but if you wish
to keep these projects separate, the responsibility then is to help your
respective user bases clearly understand the differences betwixt.  you
can do it manually (blech) or automatically.  i would suggest that
someone please develop or find code that groks your codes and lists out
(and optionally further characterizes) the interfaces.  i would like to
incorporate that grokking code in GUMM.

thi
(just another lazy meta-librarian :)