Navigation:
Browse pkgsrc
(this page)| 2009-06-16 17:25:32 by Joerg Sonnenberger | Files touched by this commit (9) |
Log message: Fix a number of GENERATE_PLIST entries to always have a terminating ; |
| 2009-06-15 00:58:11 by Joerg Sonnenberger | Files touched by this commit (129) |
Log message: Remove @dirrm related logic. |
| 2009-02-27 11:00:29 by Matthias Scheler | Files touched by this commit (1) |
Log message: Depend on "dvipsk" package because it provides the "dvips" \ binary after the recent TeX package changes. Bump package revision. |
| 2008-02-15 16:47:56 by Matthias Scheler | Files touched by this commit (1) |
Log message: Set temporary directory before invoking Ghostscript to avoid random failures when attempting to print Postscript files. Bump package revision because of this fix. Based on a patch contributed by Paul Goyette in PR pkg/38037. |
| 2007-03-24 20:21:34 by Joerg Sonnenberger | Files touched by this commit (124) |
Log message: Prepare for switching to NO_MTREE=yes. |
| 2006-08-31 10:22:38 by Roland Illig | Files touched by this commit (1) |
Log message: Added PAPERSIZE to BUILD_DEFS. Separated the code that installs the printer filters from the one that adds them to the PLIST. Converted the sed(1) command to use the SUBST framework, so that the proper install(1) commands are used for installing the files. |
| 2006-08-31 10:07:00 by Roland Illig | Files touched by this commit (2) |
Log message: Fixed path to the manual page. |
| 2006-08-10 05:21:40 by Min Sik Kim | Files touched by this commit (25) |
Log message: Remove teTeX2 from TEX_ACCEPTED, because the teTeX2 packages will be removed shortly. |
| 2006-05-13 05:44:24 by Min Sik Kim | Files touched by this commit (24) |
Log message: Remove references to teTeX1. |
| 2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257) |
Log message: 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. |
New packages: