This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
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).
libgsf 1.13.3
J.H.M. Dassen (Ray) :
* Improve documentation.
Jody :
* More work on extension interface to sax import wrapper.
--------------------------------------------------------------------------
libgsf 1.13.0
Jody:
* API changes SAX wrappers for help OpenDoc and SpreadsheetML.
Kasal:
* Improve libtool versioning.
* Relax the gconf requirement.
Luciano Wolf:
* OpenDocument meta stream parser.
Sven Herzberg:
* Fix for GsfOutputGnomeVFS
API change with shlib major change -> BUILDLINK_DEPENDS bumped.
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.
Dom:
* Fix bzip output to flush if last deflate fills buffer
Jody Goldberg:
* If the file is not an OLE2 file do not change the filepos.
* Handle broken ole files that specify codepage as signed short
* Fix reading ole files > 13.6 Meg on sparc/alpha (from Xavier Roche)
* Tune validation test for LPSTR properties to handle char width > 1
* Make the impl headers for the base interfaces public as requested
* Add some directory tree wrappers
* Work around a -fstrict-alias warning for SuSE
* Move to automake-1.7
* Fix gnome-vfs backend to open files with random access
* Support merging content from nested nodes for sax parsing
* Fix gtk-doc
Joseph Frazee:
* patch the spec file.
Morten Welinder:
* Properly chain finalizer.
* Fix gzip output to flush if last deflate fills buffer
Tor Lillqvist:
* packaging tools for win32.
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.
