NetBSD sort objects to setting the field separator to the same value as
the record separator. Since in this case the surrounding code guarantees
there will be no tabs in the input set the field separator to tab.
Bump PKGREVISION.
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).
so that on 64bit systems it is actually a negative number, not a very
large positive one. Should fix PR pkg/29351.
Thanks to Martijn van Buul for giving me access to an amd64 box so I
could track this down. Bump PKGREVISION.
Quote from the commit log(ports/editors/emacs21/Makefile version 1.10).
-----------------------------------------
Work around the fact that emacs undump knows too much about the layout
of elf files (or thinks it does). These assumptions were just broken
by binutils/ld changes to put GOT and PLT into their own PT_LOAD sections.
Thus BSS is no longer part of the DATA PT_LOAD section. This is a
workaround using the '-Z' compatibility flag which disables the GOT/PLT
padding.
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.
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.
Changes from etc/NEWS:
** The obsolete C mode (c-mode.el) has been removed to avoid problems
with Custom.
** UTF-16 coding systems are available, encoding the same characters
as mule-utf-8. Coding system `utf-16-le-dos' is useful as the value
of `selection-coding-system' in MS Windows, allowing you to paste
multilingual text from the clipboard. Set it interactively with
C-x RET x or in .emacs with `(set-selection-coding-system
'utf-16-le-dos)'.
** There is a new language environment for UTF-8 (set up automatically
in UTF-8 locales).
** Translation tables are available between equivalent characters in
different Emacs charsets -- for instance `e with acute' coming from
the
Latin-1 and Latin-2 charsets. User options
`unify-8859-on-encoding-mode'
and `unify-8859-on-decoding-mode' respectively turn on translation
between ISO 8859 character sets (`unification') on encoding
(e.g. writing a file) and decoding (e.g. reading a file). Note that
`unify-8859-on-encoding-mode' is useful and safe, but
`unify-8859-on-decoding-mode' can cause text to change when you read
it and write it out again without edits, so it is not generally
advisable.
By default `unify-8859-on-encoding-mode' is turned on.
** In Emacs running on the X window system, the default value of
`selection-coding-system' is now `compound-text-with-extensions'.
If you want the old behavior, set selection-coding-system to
compound-text, which may be significantly more efficient. Using
compound-text-with-extensions seems to be necessary only for decoding
text from applications under XFree86 4.2, whose behaviour is actually
contrary to the compound text specification.
patch. The previous one had decode-coding string<f> bug. Pointed out and
tested by tron. Thanks!
* XIM patch by Seiichiro Inouse <ginouse at ts dot catv dot ne dot jp>.
* Belately Buildlinkify.
Let's bump revision to 2.
Remove `-p' from mkdir arguments, it is already part of ${MKDIR}.
While here substitute a couple of ${PREFIX} by `%D' in
`@exec ${MKDIR} ...' lines and add a couple of missing `%D' in such lines too!
Summary of changes:
- removal of USE_GTEXINFO
- addition of mk/texinfo.mk
- inclusion of this file in package Makefiles requiring it
- `install-info' substituted by `${INSTALL_INFO}' in PLISTs
- tuning of mk/bsd.pkg.mk:
removal of USE_GTEXINFO
INSTALL_INFO added to PLIST_SUBST
`${INSTALL_INFO}' replace `install-info' in target rules
print-PLIST target now generate `${INSTALL_INFO}' instead of `install-info'
- a couple of new patch files added for a handful of packages
- setting of the TEXINFO_OVERRIDE "switch" in packages Makefiles requiring it
- devel/cssc marked requiring texinfo 4.0
- a couple of packages Makefiles were tuned with respect of INFO_FILES and
makeinfo command usage
See -newly added by this commit- section 10.24 of Packages.txt for
further information.
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
Emacs-20.6 is a bug-fix release with one user-visible change
* Support for ARM-based non-RISCiX machines has been added.
(patches/patch-be was removed because of this addition).
I believe it can run on any ports on which Emacs-20.5a runs.
after an IPv6 connection fails.
Patch supplied by Love<lha@stacken.kth.se>. Thank you!
In addition configure script and pkgsrc Makefile is modified to
be able to disable IPv6 support, looking at USE_INET6 (Makefile)
and --without-ipv6 (configure).
Minoura Makoto in PR pkg/9014. This version fixes several bugs discovered
since version 20.3 and support a precompiled user startup file (".emacs.el"
and ".emacs.elc").
This works on e.g. NetBSD/i386 (and probably other new-to-ELF ports),
as well as NetBSD/alpha. It also looks like it'll work on powerpc, though
mips may have problems. If possible, this is probably the 'right' way
to do this.
