(CVE-2006-0224 was already fixed by patch-aa in pkgsrc).
XXX: self test failed on NetBSD-5.0.1, but old version also failed.
Changes: The string class is now both an interface and an implementation, so
parallel implementations (e.g., a glib string wrapper) can be created. Detection
of Imlib2 support and a pixmap leak when it was disabled have been fixed. Fixes
have been made for gcc4/newer autotools. This release also contains a fix for
CVE-2006-0224, a buffer overflow which could lead to privilege escalation in set
uid/setgid apps using LibAST's configuration engine.
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
seems optional, but we were using it anyway. Furthermore, imlib2 also
requires it, which is a dependency for this one, so there is no problem
in doing this. Problem noted by Sebastian Prause in tech-pkg@.
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.
o only include it in the BUILD_DEFS if the current platform is concerned.
For now that only includes i386, but we might find amd64 users in the
future.
o test against [Yy][Ee][Ss], for consistency.
Fixes part of PR 26243.
DESCR:
The Library of Assorted Spiffy Things (LibAST - formerly libmej) was
originally designed as a companion library to Eterm. However, it
contains many features that other projects may find useful, so it
has been broken out into its own library. Features include thorough
debugging and memory tracking engines, various string manipulation
functions, and a flexible config file parsing engine.
