assessment of XML documents in accord with the
W3C XML Schema specification, second edition.
XSV (XML Schema Validator) is an open source (GPLed) work-in-progress
attempt at a conformant schema-aware processor, as defined by
XML Schema Part 1: Structures, Second Edition of 28 October 2004.
It has been developed at the Language Technology Group of the Human
Communication Research Centre in the School of Informatics at the
University of Edinburgh, with support for one of us (Thompson)
from the World Wide Web Consortium.
WWW: http://www.ltg.ed.ac.uk/~ht/xsv-status.html
libraries built by the previous version of the Ada compiler can not
be used by the new compiler. Rev bump a couple of libraries that can
cause breakage on incremental builds.
Reported by: pkg-fallout
- Remove USE_GNOME=intlhack. Does not do anything.
- Staging.
- Remove SKIM support. It depends on KDE3.
- Touch config.h.in in post-patch so the makefile doesn't think it's
outdated and decides to run autoheader and other autotools.
- Remove references to FreeBSD 4.x from pkg-message.
PR: ports/187011
Approved by: maintainer timeout (3 weeks)
XML EZ_Out is a small set of packages intended to aid the creation of
XML-formatted output from within Ada programs. It basically wraps the
tags and data provided to it with XML syntax and writes them to a
user-supplied medium.
This medium can be any sort of writable entity, such as a file, a
memory buffer, or even a communications link, such as a socket. The
only functionality required of the medium is that it supply a
meaningful "Put" (for writing a string) and "New_Line" procedure.
WWW: http://www.mckae.com/xmlEz.html
OpenToken is a facility for performing token analysis and parsing within
the Ada language. It is designed to provide all the functionality of a
traditional lexical analyzer/parser generator, such as lex/yacc. But due
to the magic of inheritance and runtime polymorphism it is implemented
entirely in Ada as withed-in code. No precompilation step is required, and
no messy tool-generated source code is created. The tradeoff is that the
grammar is generated at runtime.
WWW: http://stephe-leake.org/ada/opentoken.html
Rather than specify gnat_util every time ASIS is a dependency, set it
as a library dependency for ASIS. LIB_DEPENDS doesn't work because it
is a static library, so just manually add libgnat_util.a to BUILD_DEPENDS
and RUN_DEPENDS, then adjust 3 ports accordingly.
- Enable testing when MAINTAINER_MODE is set
Changes:
* More initial whitespace fixes and off-by-one errors when parsing streams
causes invalid XMLs and therefore Expat parsing errors.
(reported by Anup Rao)
At least with the upcoming gcc49 and ASIS 2013, I've been seeing gmake
Makefile-based builds trying to rebuild ASIS rather than just use the
provided static library. I don't know what causes that, but I did notice
that it doesn't happen with GNAT project files.
1) Disregard gmake completely and provide a new build.gpr file
This will work when gcc-aux is moved to gcc49.
2) Add DOCS option and install the html documentation optionally
3) Relocate LICENSE to make portlint happy
4) Using GPR makes this jobs safe (although the job number might be
limited to 1 anyway in this case)
improving accessibility.
I think people who want to just find the port/package and install it are
more likely to look for "spamassassin the program" than "spamassassin the
perl module collection."
