Hello Steve,
On Wed, Jul 20, 2005 at 05:25:35PM -0500, Steve Greenland wrote:
> I think 2 min/pkg for *spotting* problems is reasonable, but not nearly
> enough for fixing them. Decent writing is non-trivial.
Especially for cases like where some research is necessary to find out
what the package actually does. Some randomly chosen examples where
the function of the package is not clear to me from reading the
description:
djview:
DjVu viewer djview.
libaca0:
This is the files for ACA which are needed to compile binaries
from sources. There aren't any documentations, only examples yet.
libsvncpp0:
Shared library package.
libcml-smlnj:
An SML library for message-passing concurrency.
libocc0c2:
OpenC++ is a tool for source-code translation for C++.
libx500-dn-perl:
style DN strings.
.
mpdconn.app:
MPDCon is a simple GNUstep controller for MPD.
netcdfg-dev:
Includes headers, static libraries, and documentation.
riece-lsdb:
This package is cooperates with LSDB.
xjokes:
xjokes contains 4 jokes. yasiti, blackhole, mori1, and mori2.
It might also be easy to spend time on deciding whether the following
should be improved.
LibAST is the Library of Assorted Spiffy Things. It contains many
spiffy things, and it is a library. Thus, the ever-so-creative
name. LibAST has been previously known as libmej, the Eterm helper
library which nobody really understood and certainly never used.
My current plan is to gradually remove some of the neat stuff from
Eterm that could be made generic (things like the theme parsing
engine, the command-line options parser, perhaps the event engine,
...) and place it here in the hopes that others will find them
useful.
But however long it takes, some concerted effort should be able
to improve things a lot. I would be interested to help with this.
All the best,
Jochen
--
http://seehuhn.de/
Attachment:
signature.asc
Description: Digital signature