Commit graph

10 commits

Author SHA1 Message Date
joerg
3b0d97b0de Add DESTDIR support. 2008-06-20 01:09:05 +00:00
rillig
2829e658f2 Mechanically replaced man/* with ${PKGMANDIR}/* in the definition of
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.
2007-01-07 09:13:46 +00:00
jlam
9c8b5ede43 Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
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-03-04 21:28:51 +00:00
seb
37d945e229 Lower expectations, both others' and mine: relinquish stewardship 2005-12-27 13:54:57 +00:00
seb
4cf09ba7cb Set AWK properly for NetBSD. Noticed by mrg@.
Bump PKGREVISION.
2005-09-28 20:59:08 +00:00
rillig
5946936ffc Replaced "# defined" with "yes" in Makefile variables like GNU_CONFIGURE,
NO_BUILD, USE_LIBTOOL.
2005-09-28 20:52:18 +00:00
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
agc
d81d19f8e0 Add RMD160 digests. 2005-02-24 12:51:41 +00:00
seb
9b9b9ca36e Change default TMPDIR to more modern /var/tmp instead of /usr/tmp.
Claim stewardship.

Bump PKGREVISION to 1.
2005-02-09 08:40:33 +00:00
agc
65d3881c3c Initial import of vip, a script which lets you edit data (via $EDITOR
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.
2004-07-14 11:41:52 +00:00