Package: wnpp
Severity: wishlist
I've packaged REXML, a XML parser for Ruby, and intend to upload in a few
days if there aren't any objections.
There is already another pure-Ruby XML parser (NQXML) in the distribution
but this one has a (IMHO) nicer API and supports XML Namespaces and
(some) XPath expressions. If am heavily using it myself and upstream is
very active for bug-fixing and developing. The licence is the same as
Ruby (dual-licence: GPL or custom ).
Package: librexml-ruby
Architecture: all
Depends: libruby (>= 1.6.5)
Description: pure Ruby non-validating XML parser supporting Namespaces & XPath
REXML is a XML parser for Ruby written purey in Ruby so you don't need
to install any binary libraries. Currently it only ncludes a DOM-like
API which fits the Ruby-way of human-oriented programming much more than
the DOM, but a SAX-like streaming API is in the works. Additionally you
can apply (limited) XPath-expressions to the tree. REXML also has support
for XML-Namespaces.
It was downloaded from http://www.germane-software.com/~ser/Software/rexml/
Upstream Author: Sean Russell <ser@germane-software.com>
Copyright:
REXML is copyrighted free software by Sean Russell <ser@germane-software.com>.
You can redistribute it and/or modify it under either the terms of the GPL
(see /usr/share/common-licenses/GPL), or the conditions below:
1. You may make and give away verbatim copies of the source form of the
software without restriction, provided that you duplicate all of the
original copyright notices and associated disclaimers.
2. You may modify your copy of the software in any way, provided that
you do at least ONE of the following:
a) place your modifications in the Public Domain or otherwise
make them Freely Available, such as by posting said
modifications to Usenet or an equivalent medium, or by allowing
the author to include your modifications in the software.
b) use the modified software only within your corporation or
organization.
c) rename any non-standard executables so the names do not conflic
with standard executables, which must also be provided.
d) make other distribution arrangements with the author.
3. You may distribute the software in object code or executable
form, provided that you do at least ONE of the following:
a) distribute the executables and library files of the software,
together with instructions (in the manual page or equivalent)
on where to get the original distribution.
b) accompany the distribution with the machine-readable source of
the software.
c) give non-standard executables non-standard names, with
instructions on where to get the original software distribution.
d) make other distribution arrangements with the author.
4. You may modify and include the part of the software into any other
software (possibly commercial). But some files in the distribution
are not written by the author, so that they are not under this terms.
5. The scripts and library files supplied as input to or produced as
output from the software do not automatically fall under the
copyright of the software, but belong to whomever generated them,
and may be sold commercially, and may be aggregated with this
software.
6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
--
Oliver M. Bolzer
oliver@gol.com
GPG (PGP) Fingerprint = 621B 52F6 2AC1 36DB 8761 018F 8786 87AD EF50 D1FF
Attachment:
pgpkMuovXXc4J.pgp
Description: PGP signature