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).
Support Python 2.4
1.1.1 changes:
numarray-1.1.1 is a bugfix release to numarray-1.1. Notable bugs
fixed include memory leaks in matrixmultiply and comparison ufuncs.
1.1 changes:
I. ENHANCEMENTS
CharArray eval() sped up
Document memmap.py (memory mapping)
Unsigned int type support limited
Add kroenecker product
II. BUGS FIXED / CLOSED
max.reduce of byteswapped array
numeric compatibility byteoffset
matrixmultiply (a,b) leaves b transposed
random_array.randint exceeds boundaries
buffer not aligned on 8 byte boundary (Windows-98 broken)
Object Array repr for >1000 elements
Invalid sequences errors
Segfault in array element deletion
Incorrect handling of overlapping assignments in Numarray
Weirdness with 'new' method
searchsorted bug and fix
randint bug fix patch
a.is_c_array() mixed int/bool results
argsort of string arrays
III. CAUTIONS
1. This release is binary incompatible with numarray-1.0. Writers of
C-extensions which directly reference the byteoffset field of the
PyArrayObject should be aware that the data pointer is now the sum of
byteoffset and the buffer base pointer. All C extensions which use
the numarray C-API must be recompiled. This incompatibility was an
unfortunate consequence of the fix for "numeric compatibility
byteoffset".