summaryrefslogtreecommitdiff
path: root/textproc/gsed
AgeCommit message (Collapse)AuthorFilesLines
2011-04-22recursive bump from gettext-lib shlib bump.obache1-1/+2
2010-05-02Update to 4.2.1:wiz2-6/+6
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
2009-08-08Update to 4.2:wiz8-118/+13
* 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 `.'
2008-04-04DESTDIR supported.joerg1-1/+2
2007-12-19Fixed a typo in the patch for regcomp.rillig2-4/+4
2007-12-19Fixed the build on Solaris with the Sun C compiler. Like many otherrillig4-6/+62
pieces of GNU software, this package makes use of GCC extensions. Another thing is that on Solaris, <stdbool.h> may only be included by the c99 compiler, not any other; therefore we need to define our boolean type ourself.
2007-04-10Kill a completely bogus fragment of configure (also dead upstream)joerg3-5/+33
and fix the issue in po/Makefile.in.in directly.
2007-03-08Update to 4.1.5:wiz6-43/+27
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
2007-02-22Whitespace cleanup, courtesy of pkglint.wiz1-4/+4
Patch provided by Sergey Svishchev in private mail.
2006-11-05This package wants USE_TOOLS+=makeinfo, at least under my environment.dsainty1-2/+2
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.
2006-04-17Strip ${PKGLOCALEDIR} from PLISTs of packages that already obeyjlam1-32/+32
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-07List info files directly in the PLIST and honor PKG{INFO,MAN}DIR.jlam2-3/+4
2006-04-07Remove patch made unnecessary by makeinfo replacement script.jlam2-15/+1
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
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.
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg1-2/+2
2005-12-27Lower expectations, both others' and mine: relinquish stewardshipseb1-2/+2
2005-12-05Ran "pkglint --autofix", which corrected some of the quoting issues inrillig1-2/+2
CONFIGURE_ARGS.
2005-12-05Fixed pkglint warnings. The warnings are mostly quoting issues, forrillig1-2/+2
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
2005-05-22Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:jlam1-2/+2
USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-03-01add grep to GNU_TOOLS. Needed on solaris.dmcmahill1-1/+4
2005-02-24Add RMD160 digests to the SHA1 ones.agc1-1/+2
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-1/+2
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.
2004-07-07Update to version 4.1.1.seb4-5/+32
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
2004-06-25Update to version 4.1.seb5-46/+7
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-05-08Enable pkgviews installation.uebayasi1-1/+3
2004-04-25Convert to buildlink3 and fix a spelling error in DESCR.snj2-5/+5
2004-03-10Remove info files entries from PLIST.seb1-4/+1
2004-02-10remove a rogue trailing /, fixes build problem reported by Alexgrant2-1/+15
Gontcharov on tech-pkg. fix from Charlie Allom.
2004-01-21Update to 4.09:wiz3-6/+7
* 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.
2003-12-13Update to version 4.08.seb4-20/+12
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-10-07Add TEST_TARGET and fix tests on Solarisheinz4-3/+41
2003-08-09USE_NEW_TEXINFO is unnecessary now.seb1-2/+1
2003-08-02no longer needed.grant1-56/+0
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-07-09enhancements to gracefully handle packages which require a non-brokengrant1-8/+38
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.
2003-07-03Convert to USE_NEW_TEXINFO.seb2-5/+3
2003-06-14improve COMMENTgrant1-2/+2
2003-06-14Update gsed to 4.0.7.grant5-51/+65
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-13improvegrant1-1/+8
2003-04-16Provide a buildlink structure so sed and gsed appear in buildlink/bin as somejmc1-0/+26
programs require GNU sed, but refer to 'sed' directly in their scripts.
2003-02-18These packages have been converted to use buildlink2, so they no longerjlam1-2/+1
need to use the automake-override target in bsd.pkg.mk; the hide-autotools target in bsd.buildlink2.mk accomplishes the same thing.
2002-12-25Honor GNU_PROGRAM_PREFIX. Patch by Jeremy C. Reed.wiz2-5/+13
2002-08-25Merge packages from the buildlink2 branch back into the main trunk thatjlam1-1/+2
have been converted to USE_BUILDLINK2.
2002-02-18Introduce new framework for handling info files generation and installation.seb2-4/+5
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.
2001-12-04By default, prevent invocation of GNU "auto*" driven by the generatedjlam1-2/+1
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.
2001-10-31Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-10-29To avoid build dependencies on auto* tools a patch on configure scriptseb3-12/+36
(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.
2001-09-28If automake is called with -i, we don't need gmake.wiz1-3/+2
Patch from Stoned Elipot in pkg/14082.
2001-06-26Initial import of gsed-3.02, GNU sed.wiz5-0/+51
Packaged by Stoned Elipot, and sent via pkg/13238; for use with Zoularis.