Commit graph

16 commits

Author SHA1 Message Date
wiz
2c4a867040 Update to 4.2.2:
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.
2013-01-06 00:35:40 +00:00
cheusov
e960923249 Add symlink gnu/man/man1/sed
++pkgrevision
2012-06-01 19:29:38 +00:00
cheusov
22270d8758 Remove GNU_PROGRAM_PREFIX variable (discussed in pkgsrc-users@).
All utilities are installed with a prefix 'g'. Symlinks with original
names are created in ${PREFIX}/gnu/bin.

++pkgrevision
2012-05-29 22:22:00 +00:00
sbd
fc70b3b60b Make sure that the gsed package always has a 'gsed' executable.
Bump PKGREVISION
2011-12-29 22:30:47 +00:00
wiz
1a860c5d30 Update to 4.2:
* 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 `.'
2009-08-08 21:26:49 +00:00
jlam
ea5f9f80b6 Strip ${PKGLOCALEDIR} from PLISTs of packages that already obey
PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries.  From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
2006-04-17 07:07:11 +00:00
jlam
90bc26e8c2 List info files directly in the PLIST and honor PKG{INFO,MAN}DIR. 2006-04-07 19:54:16 +00:00
seb
02518bb0ce Update to version 4.1.
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).
2004-06-25 15:17:55 +00:00
seb
26e9a5e867 Remove info files entries from PLIST. 2004-03-10 01:54:13 +00:00
wiz
c706434e7f Update to 4.09:
* 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.
2004-01-21 22:53:22 +00:00
seb
04b79e1e31 Update to version 4.08.
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).
2003-12-13 16:36:21 +00:00
seb
6340944506 Convert to USE_NEW_TEXINFO. 2003-07-03 20:09:13 +00:00
grant
abf351ba30 Update gsed to 4.0.7.
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.
2003-06-14 00:04:55 +00:00
wiz
9fe706fe68 Honor GNU_PROGRAM_PREFIX. Patch by Jeremy C. Reed. 2002-12-25 17:51:23 +00:00
seb
66111c6d15 Introduce new framework for handling info files generation and installation.
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.
2002-02-18 15:14:00 +00:00
zuntum
d038a73ebd Move pkg/ files into package's toplevel directory 2001-10-31 22:52:58 +00:00