a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
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.
Bump BUILDLINK_ABI_DEPENDS according to library version.
Changes between 1.6.1 and 1.6.2 (21-Feb-2008 to 04-Jul-2008)
o Adjust "devtool.func" for latest GNU Libtool compatibility.
[Ralf S. Engelschall]
o Consistently annotate "RFC-XXXX" with "IETF" to clearly
indicate from which standards body this comes from.
[Ralf S. Engelschall]
o Resolve namespace conflicts of recently introduced time_xxx()
functions by using a propoer "uuid_" prefix.
[Ralf S. Engelschall]
o Remove unused "struct timezone" from time_gettimeofday() in
order to simplify portability.
[Ralf S. Engelschall]
o Add support for POSIX clock_gettime(3) in case the Unix/POSIX
gettimeofday(3) is not available.
[Ralf S. Engelschall]
o Upgrade build environment to GNU autoconf 2.62.
[Ralf S. Engelschall]
o Upgrade build environment to GNU libtool 2.2.4.
[Ralf S. Engelschall]
Changes between 1.6.0 and 1.6.1 (19-May-2007 to 21-Feb-2008)
o Fix __VA_COPY_USE_{CSP,CPP} fallback macros for va_copy.
[Mark A. Lindner <mark.a.lindner@gmail.com>]
o PostgreSQL bindings: use SET_VARSIZE() instead
of assigning to bytea->v_len under PostgreSQL >= 8.3
[Ralf S. Engelschall]
does not have files in common with sysutils/e2fsprogs, so they should
not conflict. On the other hand, the packages wip/e2fsprogs and
wip/libuuid _do_ have files in common with ossp-uuid, so I leave the
CONFLICTS line as a comment.
UUIDs are 128 bit numbers which are intended to have a high likelihood
of uniqueness over space and time and are computationally difficult
to guess. They are globally unique identifiers which can be locally
generated without contacting a global registration authority. UUIDs
are intended as unique identifiers for both mass tagging objects
with an extremely short lifetime and to reliably identifying very
persistent objects across a network.
OSSP uuid is a ISO-C:1999 application programming interface (API)
and corresponding command line interface (CLI) for the generation
of DCE 1.1, ISO/IEC 11578:1996 and RFC 4122 compliant Universally
Unique Identifier (UUID). It supports DCE 1.1 variant UUIDs of version
1 (time and node based), version 3 (name based, MD5), version 4
(random number based) and version 5 (name based, SHA-1). Additional
API bindings are provided for the languages ISO-C++:1998, Perl:5 and
PHP:4/5. Optional backward compatibility exists for the ISO-C DCE-1.1
and Perl Data::UUID APIs.
