Disable the config.status overriding, it causes config.status to be rerun...
FYI an alternative would be to use GNU make!
Changes since last packaged version:
Sed 4.1.1
* preserve permissions of in-place edited files
* yield an error when running -i on terminals or other non regular files
* do not interpret - as stdin when running in in-place editing mode
* fix bug that prevented 's' command modifiers from working
Package changes:
* remove inclusion of converters/libiconv/buildlink3.mk,
devel/gettext-lib/builtin.mk will take care of that if needed.
Changes since last packaged version (4.0.9):
* // matches the last regular expression even in POSIXLY_CORRECT mode.
* change the way we treat lines which are not terminated by a newline.
Such lines are printed without the terminating newline (as before)
but as soon as more text is sent to the same output stream, the
missing newline is printed, so that the two lines don't concatenate.
The behavior is now independent from POSIXLY_CORRECT because POSIX
actually has undefined behavior in this case, and the new implementation
arguably gives the ``least expected surprise''. Thanks to Stepan
Kasal for the implementation.
* documentation improvements, with updated references to the POSIX.2
specification
* error messages on I/O errors are better, and -i does not leave temporary
files around (e.g. when running ``sed -i'' on a directory).
* escapes are accepted in the y command (for example: y/o/\n/ transforms
o's into newlines)
* -i option tries to set the owner and group to the same as the input file
* `L' command is deprecated and will be removed in sed 4.2.
* line number addresses are processed differently -- this is supposedly
conformant to POSIX and surely more idiot-proof. Line number addresses
are not affected by jumping around them: they are activated and
deactivated exactly where the script says, while previously
5,8b
1,5d
would actually delete lines 1,2,3,4 and 9 (!).
* multibyte characters are taken in consideration to compute the
operands of s and y, provided you set LC_CTYPE correctly. They are
also considered by \l, \L, \u, \U, \E.
* [\n] matches either backslash or 'n' when POSIXLY_CORRECT.
* new option --posix, disables all GNU extensions. POSIXLY_CORRECT only
disables GNU extensions that violate the POSIX standard.
* options -h and -V are not supported anymore, use --help and --version.
* removed documentation for \s and \S which worked incorrectly
* restored correct behavior for \w and \W: match [[:alnum:]_] and
[^[:alnum:]_] (they used to match [[:alpha:]_] and [^[:alpha:]_]
* the special address 0 can only be used in 0,/RE/ or 0~STEP addresses;
other cases give an error (you are hindering portability for no reason
if specifying 0,N and you are giving a dead command if specifying 0
alone).
* when a \ is used to escape the character that would terminate an operand
of the s or y commands, the backslash is removed before the regex is
compiled. This is left undefined by POSIX; this behavior makes `s+x\+++g'
remove occurrences of `x+', consistently with `s/x\///g'. (However, if
you enjoy yourself trying `s*x\***g', sed will use the `x*' regex, and you
won't be able to pass down `x\*' while using * as the delimiter; ideas on
how to simplify the parser in this respect, and/or gain more coherent
semantics, are welcome).
* 0 address behaves correctly in single-file (-i and -s) mode.
* documentation improvements.
* tested with many hosts and compilers.
* updated regex matcher from upstream, with many bugfixes and speedups.
* the `N' command's feature that is detailed in the BUGS file was disabled
by the first change below in sed 4.0.8. The behavior has now been
restored, and is only enabled if POSIXLY_CORRECT behavior is not
requested.
Changes since 4.07:
* fix `sed n' printing the last line twice.
* fix incorrect error message for invalid character classes.
* fix segmentation violation with repeated empty subexpressions.
* fix incorrect parsing of ^ after escaped (.
* more comprehensive test suite (and with many expected failures...)
Please note that since NetBSD's sed is available in a portable
version in pkgsrc as textproc/nbsed, and in bootstrap-pkgsrc I do
not consider this package as being low in the dependencies food-chain
anymore. This is especially true for platforms other than NetBSD.
So let me explicitly add dependencies on libiconv and gettext-lib packages
(if needed of course).
sed, or perhaps GNU sed.
packges should define USE_GNU_SED if GNU sed is really required,
otherwise we provide ${SED} in the buildlink/bin dir, unless the sed
provided on a given platform is known to be severely broken.
[one could argue Solaris' xpg4 sed falls in the "broken" category, but
for almost all intents and purposes, it is acceptable - define
USE_GNU_SED if a package still fails.]
XXX IRIX is currently listed in _INCOMPAT_SED - this should be removed
if sed on IRIX is known to be good.
changes since 3.02:
4.0.7
Changes: This version fixes some rare infinite loops and wrong results
that occurred when the s command had a numeric option and the regular
expression could match the empty string.
4.0.6
Changes: This release improves portability a lot, and adds a
configure-time switch to choose between the included regex matcher and
the system matcher (on glibc systems only).
4.0.5
Changes: This release fixes a few portability bugs and improves the
quality of the documentation. "a", "i", "l", "L", and "=" now accept
address ranges.
4.0.3
Changes: A packaging problem with two missing translation catalogs was
fixed.
4.0.2
Changes: This release makes sed able to bootstrap itself on operating
systems that cannot run the configure script.
4.0.1
Changes: This release includes translations for over 20 languages, and
cleans up the binary and documentation files from references to
super-sed.
4.0
Changes: This release has been merged with super-sed and supports all
of its features, except for Perl regular expressions. This includes
in-place editing, new sed commands, better documentation, and support
for changing the case of the characters with the `s' command. The
performance and correctness of the regular expression matcher have
also been improved.
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.
Makefiles during the build process by touching various auto{conf,make}
source files to make them up-to-date. Packages that require regenerating
the configure script and Makefile.in files should make the appropriate
calls to auto{conf,make} in a pre-configure target. This allows the
various targets listed in ${_CONFIG_PREREQ} to modify the generated files
without triggering the GNU auto* tools and having the modifications be
overwritten.
(manually regenerated from patched configure.in) is added, AUTOMAKE_OVERRIDE
is also defined hence custom pre-configure target is removed.
To avoid useless makeinfo run sed.info, version.texi and stamp-vti are added
to AUTOMAKE_PATTERNS (this also fix a hidden and forgotten build dependency on
../../devel/gtexinfo).
While here my email address as maintainer is updated.