pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2008-06-20	Add DESTDIR support.	joerg	1	-3/+4

2007-01-07	Mechanically replaced man/* with ${PKGMANDIR}/* in the definition of	rillig	1	-3/+3
	INSTALLATION_DIRS, as well as all occurrences of ${PREFIX}/man with ${PREFIX}/${PKGMANDIR}. Fixes PR 35265, although I did not use the patch provided therein.
2006-03-04	Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no	jlam	1	-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.
2005-12-27	Lower expectations, both others' and mine: relinquish stewardship	seb	1	-2/+2

2005-09-28	Set AWK properly for NetBSD. Noticed by mrg@.	seb	3	-6/+16
	Bump PKGREVISION.
2005-09-28	Replaced "# defined" with "yes" in Makefile variables like GNU_CONFIGURE,	rillig	1	-3/+3
	NO_BUILD, USE_LIBTOOL.
2005-04-11	Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.	tv	1	-2/+1

2005-02-24	Add RMD160 digests.	agc	1	-1/+3

2005-02-09	Change default TMPDIR to more modern /var/tmp instead of /usr/tmp.	seb	3	-3/+18
	Claim stewardship. Bump PKGREVISION to 1.
2004-07-14	Initial import of vip, a script which lets you edit data (via $EDITOR	agc	4	-0/+63
	or $VISUAL) at any point in a pipe. From a nudge from David Maxwell. Normally, in a pipeline, when you need to edit some phase of the data stream, you use a standard tool such as sed, grep, or awk to alter, filter, or otherwise manipulate the stream. One potential problem with this approach is that the manipulations have to be very well thought out in advance. Another is that the manipulations will probably need to be applied uniformly. And third, the data must be very well understood in advance. Not all situations and data easily conform to these constraints. Alternatively, when the changes needed for the data are more than trivial, or perhaps you just don't feel like expending the mental energy needed to work out all the expressions in advance, a typical approach might be to run some process or pipeline, dump output to a file, edit the file with vi, pico, or emacs, then push the data along to the next phase by using the file as input to some additional process or pipeline. The catch here - other than the sheer awkwardness of this process - is that you have to remember to come back later and clean up all of those little and not-so-little "temporary" files. So, wouldn't you just like to be able to tap in an edit session at any arbitrary point in the pipeline, do your magic on the data, then have it automagically continue on its merry way? The vip program provides this functionality, and operates syntactically just like any other filter.