| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* Noteworthy changes in release 4.4 (2017-02-03) [stable]
** Bug fixes
sed could segfault when invoked with specific combination of newlines
in the input and regex pattern. [Bug introduced in sed-4.3]
|
|
* Noteworthy changes in release 4.3 (2016-12-30) [stable]
** Improvements
sed's regular expression matching is now typically 10x faster
sed now uses unlocked-io where available, resulting in faster I/O
operations.
** Bug fixes
sed no longer mishandles anchors ^/$ in multiline regex (s///mg)
with -z option (NUL terminated lines). [Bug introducted in sed-4.2.2
with the initial implementation of -z]
sed no longer accepts a ":" command without a label; before, it would
treat that as defining a label whose name is empty, and subsequent
label-free "t" and "b" commands would use that label. Now, sed emits
a diagnostic and fails for that invalid construct.
sed no longer accesses uninitialized memory when processing certain
invalid multibyte sequences. Demonstrate with this:
echo a | LC_ALL=ja_JP.eucJP valgrind sed/sed 's/a/b\U\xb2c/'
The error appears to have been introduced with the sed-4.0a release.
The 'y' (transliterate) operator once again works with a NUL byte
on the RHS. E.g., sed 'y/b/\x00/' now works like tr b '\0'. GNU sed
has never before recognized \x00 in this context. However, sed-3.02
and prior did accept a literal NUL byte in the RHS, which was possible
only when reading a script from a file. For example, this:
echo abc|sed -f <(printf 'y/b/\x00/\n')|cat -A
is what stopped working. [bug introduced some time after sed-3.02 and
prior to the first sed-4* test release]
When the closed-above line number ranges of N editing commands
overlap (N>1), sed would apply commands 2..N to the line just
beyond the largest range endpoint.
[bug introduced some time after sed-4.09 and prior to release in sed-4.1]
Before, this command would mistakenly modify line 5:
$ seq 6|sed '2,4d;2,3s/^/x/;3,4s/^/y/'
1
yx5
6
Now, it does not:
$ seq 6|sed '2,4d;2,3s/^/x/;3,4s/^/y/'
1
5
6
An erroneous sed invocation like "echo > F; sed -i s//b/ F" no longer
leaves behind a temporary file. Before, that command would create a file
alongside F with a name matching /^sed......$/ and fail to remove it.
sed --follow-symlinks now works again for stdin.
[bug introduced in sed-4.2.2]
sed no longer elides invalid bytes in a substitution RHS.
Now, sed copies such bytes into the output, just as Perl does.
[bug introduced in sed-4.1 -- it was also present prior to 4.0.6]
sed no longer prints extraneous character when a backslash follows \c.
'\c\\' generates control character ^\ (ASCII 0x1C).
Other characters after the second backslash are rejected (e.g. '\c\d').
[bug introduced in the sed-4.0.* releases]
sed no longer mishandles incomplete multibyte sequences in s,y commands
and valid multibyte SHIFT-JIS characters in character classes.
Previously, the following commands would fail:
LC_ALL=en_US.UTF-8 sed $'s/\316/X/'
LC_ALL=ja_JP.shiftjis sed $'/[\203]/]/p'
[bug introduced some time after sed-4.1.5 and before sed-4.2.1]
** Feature removal
The "L" command (format a paragraph like the fmt(1) command would)
has been listed in the documentation as a failed experiment for at
least 10 years. That command is now removed.
** Build-related
"make dist" now builds .tar.xz files, rather than .tar.gz ones.
xz is portable enough and in wide-enough use that distributing
only .tar.xz files is enough. It has been fine for coreutils, grep,
diffutils and parted for a few years.
** New Features
new --sandbox option rejects programs with r/w/e commands.
* Noteworthy changes in release 4.2.2 (2012-12-22) [stable]
* don't misbehave (truncate input) for lines of length 2^31 and longer
* fix endless loop on incomplete multibyte sequences
* -u also does unbuffered input, rather than unbuffered output only
* New command `F' to print current input file name
* sed -i, s///w, and the `w' and `W' commands also obey the --binary option
(and create CR/LF-terminated files if the option is absent)
* --posix fails for scripts (or fragments as passed to the -e option) that
end in a backslash, as they are not portable.
* New option -z (--null-data) to separate lines by ASCII NUL characters.
* \x26 (and similar escaped sequences) produces a literal & in the
replacement argument of the s/// command, rather than including the
matched text.
|
|
|
|
|
|
|
|
|
|
Sed 4.2.2
* don't misbehave (truncate input) for lines of length 2^31 and longer
* fix endless loop on incomplete multibyte sequences
* -u also does unbuffered input, rather than unbuffered output only
* New command `F' to print current input file name
* sed -i, s///w, and the `w' and `W' commands also obey the --binary option
(and create CR/LF-terminated files if the option is absent)
* --posix fails for scripts (or fragments as passed to the -e option) that
end in a backslash, as they are not portable.
* New option -z (--null-data) to separate lines by ASCII NUL characters.
* \x26 (and similar escaped sequences) produces a literal & in the
replacement argument of the s/// command, rather than including the
matched text.
|
|
|
|
|
|
|
|
++pkgrevision
|
|
All utilities are installed with a prefix 'g'. Symlinks with original
names are created in ${PREFIX}/gnu/bin.
++pkgrevision
|
|
Bump PKGREVISION
|
|
|
|
Sed 4.2.1
* fix parsing of s/[[[[[[[[[]//
* security contexts are preserved by -i too under SELinux
* temporary files for sed -i are not made group/world-readable until
they are complete
|
|
* now released under GPLv3
* added a new extension `z` to clear pattern space even in the presence
of invalid multibyte sequences
* a preexisting GNU gettext installation is needed in order to compile
GNU sed with NLS support
* new option --follow-symlinks, available when editing a file in-place.
This option may not be available on some systems (in this case, the
option will *not* be a no-op; it will be completely unavailable).
In the future, the option may be added as a no-op on systems without
symbolic links at all, since in this case a no-op is effectively
indistinguishable from a correct implementation.
* hold-space is reset between different files in -i and -s modes.
* multibyte processing fixed
* the following GNU extensions are turned off by --posix: options [iImMsSxX]
in the `s' command, address kinds `FIRST~STEP' and `ADDR1,+N' and `ADDR1,~N',
line address 0, `e' or `z' commands, text between an `a' or `c' or `i'
command and the following backslash, arguments to the `l' command.
--posix disables all extensions to regular expressions.
* fixed bug in 'i\' giving a segmentation violation if given alone.
* much improved portability
* much faster in UTF-8 locales
* will correctly replace ACLs when using -i
* will now accept NUL bytes for `.'
|
|
|
|
Sed 4.1.5
* fix parsing of a negative character class not including a closed bracket,
like [^]] or [^]a-z].
* fix parsing of [ inside an y command, like y/[/A/.
* output the result of commands a, r, R when a q command is found.
----------------------------------------------------------------------------
Sed 4.1.4
* \B correctly means "not on a word boundary" rather than "inside a word"
* bugfixes for platform without internationalization
* more thorough testing framework for tarballs (`make full-distcheck')
----------------------------------------------------------------------------
Sed 4.1.3
* regex addresses do not use leftmost-longest matching. In other words,
/.\+/ only looks for a single character, and does not try to find as
many of them as possible like it used to do.
* added a note to BUGS and the manual about changed interpretation
of `s|abc\|def||', and about localization issues.
* fixed --disable-nls build problems on Solaris.
* fixed `make check' in non-English locales.
* `make check' tests the regex library by default if the included regex
is used (regex tests had to be enabled separately up to now).
----------------------------------------------------------------------------
Sed 4.1.2
* fix bug in 'y' command in multi-byte character sets
* fix severe bug in parsing of ranges with an embedded open bracket
* fix off-by-one error when printing a "bad command" error
|
|
Patch provided by Sergey Svishchev in private mail.
|
|
It's not exactly clear why, since the error states:
"You should only need it [makeinfo] if you modified a `.texi' or
`.texinfo' file, or any other file indirectly affecting the aspect of
the manual."
... but it's possibly a side effect of GNU_PROGRAM_PREFIX=g. At any
rate, "makeinfo" seems a harmless request.
|
|
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
|
|
|
|
CONFIGURE_ARGS.
|
|
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in
http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
|
|
|
|
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.
|
|
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).
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
need to use the automake-override target in bsd.pkg.mk; the hide-autotools
target in bsd.buildlink2.mk accomplishes the same thing.
|
|
|
|
have been converted to USE_BUILDLINK2.
|
|
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.
|
|
Patch from Stoned Elipot in pkg/14082.
|
|
Packaged by Stoned Elipot, and sent via pkg/13238; for use with Zoularis.
|
