| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
need them, for example RESTRICTED and SUBST_MESSAGE.*.
|
|
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.
|
|
"extract" script for extraction. Many cases where a custom EXTRACT_CMD
simply copied the distfile into the work directory are no longer
needed. The extract script also hides differences between pax and
tar behind a common command-line interface, so we no longer need code
that's conditional on whether EXTRACT_USING is tar or pax.
|
|
|
|
NO_BUILD, USE_LIBTOOL.
|
|
|
|
|
|
override, and allow overriding awk implementation with $AWK. Default it
to the value of ${AWK} in platform-specific pkgsrc config.
|
|
expression is good enough to strip out the non-shell header text.
|
|
|
|
"This is awf, the Amazingly Workable Formatter -- a "nroff -man" or
(subset) "nroff -ms" clone written entirely in (old) awk.
It is slow and has many restrictions, but does a decent job on most
manual pages and simple -ms documents, and isn't subject to AT&T's
brain-damaged licensing that denies many System V users any text
formatter at all. It is also a text formatter that is simple enough
to be tinkered with, for people who want to experiment.
Type "make r" to run a regression test, formatting the manual page
(awf.1) and comparing it to a preformatted copy (awf.1.out). Type
"make install" to install it. Pathnames may need changing.
I don't know whether awf will run on 16-bit machines. Data requirements
are modest, but I fear the programs are probably big enough to run awk
out of space.
I can't believe I really wrote this.
Henry Spencer at U of Toronto Zoology
henry@zoo.toronto.edu utzoo!henry
13 July 1990"
|
