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
Highlights of this release include:
Generalized variables are now in core Emacs Lisp.
An update for the Common Lisp emulation library.
A new major mode for Python.
(The operating system support framework was changed -- Dragonfly
support might need fixes.)
The previous commit used openpty on all platforms, yet failed to ensure
it was made available for them.
Add DragonFly to the string of *BSD that require libutil for openpty.
Fixes regression caused by previous commit.
In order to fix the build on DragonFly, the locations of the crt files
had to be defined. This was tricky as DragonFly has two base compilers
so gcc --print-libgcc-file-name was used to determine the path of the
crt files.
Also patch-iisp_files.el was removed. It was removed from distinfo 5
weeks ago, but the patch itself was left in place causing "patch ignored"
warnings.
(1) CVE-2012-3479 fixed on lisp/files.el
patches/patch-lisp_files.el is removed.
(2) From: ChangeLog
-------
2012-08-24 Chong Yidong <cyd@gnu.org>
* Version 24.2 released.
2012-08-14 Ulrich Mueller <ulm@gentoo.org>
* lib/gnulib.mk:
* lib/stdio.in.h:
* m4/stdio_h.m4: Do not assume that gets is defined (Bug#11873).
2012-06-21 Ulrich Mueller <ulm@gentoo.org>
* configure.in: Use m/intel386.h for amd64 with x32 ABI. (Bug#11669)
--------
Thanks wiz@
When the Emacs user option `enable-local-variables' is set to `:safe'
(the default value is t), Emacs should automatically refuse to evaluate
`eval' forms in file-local variable sections. Due to the bug, Emacs
instead automatically evaluates such `eval' forms. Thus, if the user
changes the value of `enable-local-variables' to `:safe', visiting a
malicious file can cause automatic execution of arbitrary Emacs Lisp
code with the permissions of the user.
Bug tracker ref: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12155
When the Emacs user option `enable-local-variables' is set to `:safe'
(the default value is t), Emacs should automatically refuse to evaluate
`eval' forms in file-local variable sections. Due to the bug, Emacs
instead automatically evaluates such `eval' forms. Thus, if the user
changes the value of `enable-local-variables' to `:safe', visiting a
malicious file can cause automatic execution of arbitrary Emacs Lisp
code with the permissions of the user.
Bug tracker ref: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12155
Bump PKGREVISION.
