Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
are replaced with .include "../../devel/readline/buildlink3.mk", and
USE_GNU_READLINE are removed,
* .include "../../devel/readline/buildlink3.mk" without USE_GNU_READLINE
are replaced with .include "../../mk/readline.buildlink3.mk".
to address issues with NetBSD-6(and earlier)'s fontconfig not being
new enough for pango.
While doing that, also bump freetype2 dependency to current pkgsrc
version.
Suggested by tron in PR 47882
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.
- patch target for patch-ab and patch-configure were the same.
Merged them as patch-ab.
(Naturally Revoming patches/patch-configure.)
- Also cvs delete for patches/patch-a[ce] were missing, corrected.
libXext/buildlink3.mk, now that it is included there.
Leave the places where its API version is set or variables from it
are used directly (about 3 packages).
or USE_X11BASE set, but don't include mk/x11.buildlink3.mk directly or
via buildlink3.mks
- introduce BUILDLINK_PREFIX.libXpm as alias for BUILDLINK_PREFIX.xpm
in the !modular case
- fix some cases where the check for libX11 couldn't work at all by using
C++ for compilation without including the proper headers
Verified using a full X11_TYPE=xorg bulk build without additional
breakage. Discussed with salo@, wiz@ and send to packages@ for feedback.
packages with the modular Xorg equivalent. Those are falling back
to the old location by default, so this commmit doesn't change
dependencies.
graphics/xpm ==> x11/libXpm
fonts/Xft2 ==> x11/libXft
x11/Xfixes ==> x11/libXfixes
x11/xcursor ==> x11/libXcursor
x11/Xrender ==> x11/libXrender
x11/Xrandr ==> libXrandr
fvwm-2.4.20 maintenance release for all earlier 2.4.x versions.
It contains a number of minor fixes and one important security fix.
This release is available at the home page: http://www.fvwm.org/.
Who needs to upgrade?
---------------------
Because of the security issues with fvwm-2.3.4 to fvwm-2.4.19, it
is strongly recommended to upgrade to fvwm-2.4.19.
System administrators are encouraged to install this version to
grant their users access to the latest stable version.
Bug Fixes:
----------
* The configure script now correctly appends executable file
extensions to conditionally built binaries. Fixes building on
Cygwin.
* FvwmConsole no longer conflicts with getline of Cygwin's stdio.
* Fixed parsing of For loops in FvwmScript.
* Fixed a possible endless loop when de-iconifying a transient
window.
* Reject some invalid GNOME hints.
* Fixed a loop when xterm changes its "active icon" size.
* The configure script can now cope with four-part version numbers
when detecting some libraries.
* Security fixes in
fvwm-menu-directory. (CVE-2006-5969)
FvwmCommand
