Commit graph

23 commits

Author SHA1 Message Date
joerg
68e360cc87 Use config file framework for efax.rc. Bump revision. 2006-04-12 23:04:21 +00:00
jlam
daad0f3d6c Modify the pkginstall framework so that it manages all aspects of
INSTALL/DEINSTALL script creation within pkgsrc.

If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts.  If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:

	INSTALL_SRC=	${PKGDIR}/INSTALL
	DEINSTALL_SRC=	# emtpy

As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts.  By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).

In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework.  The only public variables relating to the templates are:

	INSTALL_SRC		INSTALL_TEMPLATE
	DEINSTALL_SRC		DEINSTALL_TEMPLATE
				HEADER_TEMPLATE

The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
2006-03-14 01:14:26 +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
jlam
dc9594e09d Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mk
automatically detects whether we want the pkginstall machinery to be
used by the package Makefile.
2005-12-29 06:21:30 +00:00
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
agc
645a2eab08 Add RMD160 digests in addition to SHA1 ones. 2005-02-23 16:05:29 +00:00
jlam
5e5ac5cef9 USE_BUILDLINK3 is a yes/no variable. 2004-11-13 21:28:27 +00:00
recht
9ae9cb40d9 Don not use {head,tail} -n since it is not supported by some
implementations.
patch provided by Georg Schwarz in PR 26789
2004-08-29 16:07:29 +00:00
snj
bffc80c64f Convert to buildlink3. 2004-04-11 05:59:14 +00:00
jlam
b2677a2cb0 Add definitions for DEINSTALL_EXTRA_TMPL and INSTALL_EXTRA_TMPL if
USE_PKGINSTALL is "YES".  bsd.pkg.install.mk will no longer automatically
pick up a INSTALL/DEINSTALL script in the package directory and assume that
you want it for the corresponding *_EXTRA_TMPL variable.
2003-08-30 22:51:11 +00:00
jlam
80f85d8b31 Convert to use bsd.pkg.install.mk. 2003-08-30 18:40:06 +00:00
martti
e69ab8c365 COMMENT should start with a capital letter. 2003-07-21 16:35:12 +00:00
grant
91f00f1cbc s/netbsd.org/NetBSD.org/ 2003-07-17 21:21:03 +00:00
markd
9d330e06c2 misc/kdeutils3 no longer provides an efax, no longer conflicts with
comms/efax. Noted by Stoned Elipot in PR 21884.
2003-06-16 13:31:44 +00:00
jschauma
e366d0c694 Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.
Should anybody feel like they could be the maintainer for any of thewe packages,
please adjust.
2003-06-02 01:15:31 +00:00
jtb
03c0fc77b5 kdeutils install an efax program conflicting with comms/efax. 2003-02-18 00:35:50 +00:00
jlam
8fdf4e7f9b buildlink1 -> buildlink2 2002-11-14 23:50:45 +00:00
wiz
b2f1a78d09 Add RCS Id. 2002-07-02 12:41:43 +00:00
hubertf
09c1f15d9d Adjust format a bit:
* 75 * '='
 * RCS ID
 * blank line
 * message text
 * optional blank line
 * 75 * '='
2001-11-11 06:17:26 +00:00
zuntum
d8ed248248 Move pkg/ files into package's toplevel directory 2001-10-31 20:43:56 +00:00
jlam
bb98a4c610 Mark as USE_BUILDLINK_ONLY. 2001-08-19 04:48:33 +00:00
jtb
5828e116e1 Add the homepage for efax. 2001-06-21 04:43:29 +00:00
jtb
3f88197883 Initial import of efax.
efax is a small ANSI C/POSIX program that sends and receives faxes
using any fax modem (Class 1, 2 or 2.0).

efax is smaller and easier to install than HylaFAX or mgetty+sendfax.
As one user put it ``EFAX is a nice simple program for single user
systems.''

The ``fax'' command, a shell script, lets you send, receive, view and
print faxes.  In larger systems, faxes can be sent by printing to a
``fax'' printer and received faxes can be e-mailed as MIME attachments
to an administrator for distribution.  efax can also pass incoming
data calls to a getty program.

The efax package includes ``efix,'' a program to convert between
various image file formats.  To fax Postscript files you will need
Ghostscript.  To view faxes you can use any program that displays PGM
files.  efix can convert received files to Postscript or HP Laserjet
formats for printing.

efax is distributed under the terms of the GNU General Public License.
2001-05-21 22:26:59 +00:00