Major updates since version 1.9 include:
* Support for XML 1.1 and Namespaces in XML 1.1.
* Added support for IBM XLC 7.0 compiler on Linux.
* Improved and stabilized C pluggable memory management functionality.
* Various improvements in Xalan XML serializers for better performance and stability.
* Upgrade from Xerces-C 2.6 to Xerces-C 2.7.
Major updates since version 1.8 include:
* Pluggable Memory Management. This feature allows applications to maintain
precise control over memory allocations. This will allow users, with
knowledge of their application's characteristics, to provide a more
efficient allocation method than the general purpose procedures provided
by the system. for more information on how to use this feature, please see
the Pluggable Memory Management section of the Programming page.
* Improved stability on the execution of large stylesheets and XML documents.
Because the current implementation relies on function recursion, certain
stylesheets/input documents may cause the program stack to overflow and
cause the application to fail. It also may inhibit executing stylesheets
that are heavily dependent on recursive functions. This feature will
prevent these types of failure.
* Provided a global option to pool all text node strings. This feature
allows developers to set a flag to determine if a parsed source tree will
pool the values of all of the text nodes in the XML document. By doing so,
this can result in a significant reduction in memory usage, particularly
if there are a lot of repeated values in text nodes. Please see the class
descriptions for XalanSourceTreeDocument, XalanDefaultParsedSource, and
XalanTransformer in the API Reference section for more information.
... and more, see: http://xml.apache.org/xalan-c/whatsnew.html
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
