libpathanValidating XML parser from the Apache XML Project
2.0_1textprocΣ=0 2.0_1Version of this port present on the latest quarterly branch.
DEPRECATED: Does not build and upstream has discontinued the project and advises that it has been replaced by textproc/xqilla This port expired on: 2013-01-04
There is no maintainer for this port.
Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
The Pathan project grew out of DecisionSoft's work on XMLScript , an
XML transformation language.
XPath was adopted as a node selection language by XMLScript when the XPath
specification was ratified by the W3C. DecisionSoft's XMLScript processor
is based on Xerces-C, a Document Object Model compliant XML parser. Pathan
therefore was designed from the base up to be fully compatible with the
Xerces parser.
Pathan 1 represents the open sourcing of the XPath component of
DecisionSoft's XMLScript processor. Pathan 1 features a full implementation
of the XPath 1.0 Specification. Pathan 1 implements the W3C DOM Level 3
XPath Specification (Working Draft February 08 2002) providing a powerful
and coherent interface between XPath and DOM and hence a standardised
interface with Xerces.
Pathan is provided to the community as we feel that the Pathan module
increases the scope and usefulness of the Xerces-C library and will be
an aid to other XML developers in their projects.
For information on Pathan 1 please see their homepage
WWW: http://software.decisionsoft.com/
2013-01-04 ports-mgmt/portmanager: Does not support modern ports features such
as MOVED, is lacking upstream and active contributions, and does not support
pkgng. Consider using ports-mgmt/portmaster, ports-mgmt/portupgrade or pkgng.
2013-01-04 net-im/openfetion: Abandoned upstream
2013-01-04 textproc/libpathan: Does not build and upstream has discontinued the
project and advises that it has been replaced by textproc/xqilla
2013-01-01 java/sun-wtk: no more public distfiles, merged with Java ME SDK 3.0
upstream
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
- s,INSTALLS_SHLIB,USE_LDCONFIG,g
- these include security/ sysutils/ textproc/ maintained by ports@
PR: ports/101916
Submitted by: Gea-Suan Lin <gslin_AT_gslin dot org>
Mass-conversion to the USE_AUTOTOOLS New World Order. The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.
Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.
Preliminary documentation can be found at:
http://people.FreeBSD.org/~ade/autotools.txt
which is in the process of being SGMLized before introduction into the
Porters Handbook.
Light blue touch-paper. Run.
Whoa there, boy, that's a mighty big commit y'all have there...
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
