[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2011Q3 2008-06-20T01:09:05Z 2008-06-20T01:09:05Z joerg joerg 2008-06-20T01:09:05Z urn:sha1:d8368bbc25c90072a19b5e48f0fba26251b6877f 2007-01-07T09:13:46Z rillig rillig 2007-01-07T09:13:46Z urn:sha1:87e1bea888d90a6044a18e46681bc456ea30305c 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-04T21:28:51Z jlam jlam 2006-03-04T21:28:51Z urn:sha1:48ff096d36ac47701672a4f682e7c4ebafea1eb9 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-27T13:54:57Z seb seb 2005-12-27T13:54:57Z urn:sha1:fac6a3269f621ea6c98f635d9a475f6963eab89c 2005-09-28T20:59:08Z seb seb 2005-09-28T20:59:08Z urn:sha1:ba53b06a9fed87a1313b0d508c70ff53502e162d Bump PKGREVISION. 2005-09-28T20:52:18Z rillig rillig 2005-09-28T20:52:18Z urn:sha1:497cdd7125f8abe86eec13bb709ecc6625e715f0 NO_BUILD, USE_LIBTOOL. 2005-04-11T21:44:48Z tv tv 2005-04-11T21:44:48Z urn:sha1:2560f48b2f5afa9fcb23e0718a2e2727ca7824cc 2005-02-09T08:40:33Z seb seb 2005-02-09T08:40:33Z urn:sha1:097a2e9e062f74a353c6894c614f6d4b8b666a02 Claim stewardship. Bump PKGREVISION to 1. 2004-07-14T11:41:52Z agc agc 2004-07-14T11:41:52Z urn:sha1:95a2879fe8c0d2781d30c29c99ce2f3195afd8e9 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.