pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2017-09-26	*: remove qt3 and the packages using it, including KDE3	wiz	1	-3/+1
	Announced in https://mail-index.netbsd.org/pkgsrc-users/2017/09/10/msg025556.html
2017-08-01	Follow some http -> https redirects.	wiz	1	-2/+2

2016-09-08	Use PKGMANDIR.	jperkin	2	-4/+4

2015-11-03	Add SHA512 digests for distfiles for comms category	agc	1	-1/+2
	Existing SHA1 digests verified, all found to be the same on the machine holding the existing distfiles (morden). Existing SHA1 digests retained for now as an audit trail.
2012-10-03	Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.	asau	1	-3/+1

2010-06-03	Add -dMaxStripSize=0 to default ghostscript command line in efax.rc	sborrill	3	-15/+23
	configuration file so that efax continues to work with ghostscript 8.71 and later (also tested backward compatibility with 8.63). Bump PKGREVISION
2010-01-29	DESTDIR support	joerg	3	-9/+13

2009-06-14	Remove @dirrm entries from PLISTs	joerg	1	-2/+1

2006-04-12	Use config file framework for efax.rc. Bump revision.	joerg	4	-7/+13

2006-03-14	Modify the pkginstall framework so that it manages all aspects of	jlam	1	-5/+1
	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-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-29	Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mk	jlam	1	-2/+1
	automatically detects whether we want the pkginstall machinery to be used by the package Makefile.
2005-04-11	Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.	tv	1	-2/+1

2005-02-23	Add RMD160 digests in addition to SHA1 ones.	agc	1	-1/+2

2004-11-13	USE_BUILDLINK3 is a yes/no variable.	jlam	1	-2/+2

2004-08-29	Don not use {head,tail} -n since it is not supported by some	recht	1	-5/+5
	implementations. patch provided by Georg Schwarz in PR 26789
2004-04-11	Convert to buildlink3.	snj	1	-2/+2

2003-08-30	Add definitions for DEINSTALL_EXTRA_TMPL and INSTALL_EXTRA_TMPL if	jlam	1	-2/+5
	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	Convert to use bsd.pkg.install.mk.	jlam	3	-28/+34

2003-07-21	COMMENT should start with a capital letter.	martti	1	-2/+2

2003-07-17	s/netbsd.org/NetBSD.org/	grant	1	-2/+2

2003-06-16	misc/kdeutils3 no longer provides an efax, no longer conflicts with	markd	1	-2/+2
	comms/efax. Noted by Stoned Elipot in PR 21884.
2003-06-02	Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.	jschauma	1	-2/+2
	Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2003-02-18	kdeutils install an efax program conflicting with comms/efax.	jtb	1	-1/+3

2002-11-14	buildlink1 -> buildlink2	jlam	1	-4/+2

2002-07-02	Add RCS Id.	wiz	1	-1/+1

2001-11-11	Adjust format a bit:	hubertf	1	-1/+3
	* 75 * '=' * RCS ID * blank line * message text * optional blank line * 75 * '='
2001-10-31	Move pkg/ files into package's toplevel directory	zuntum	5	-2/+2

2001-08-19	Mark as USE_BUILDLINK_ONLY.	jlam	1	-1/+3

2001-06-21	Add the homepage for efax.	jtb	1	-2/+3

2001-05-21	Initial import of efax.	jtb	10	-0/+294
	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.