Navigation:
Browse pkgsrc
(this page)| 2011-12-17 11:15:28 by Steven Drake | Files touched by this commit (1) |
Log message: Add missing mk/curses buildlink. Bump PKGREVISION |
| 2010-01-29 23:58:10 by Joerg Sonnenberger | Files touched by this commit (1) |
Log message: DESTDIR ready |
| 2009-08-25 14:32:56 by Thomas Klausner | Files touched by this commit (15) |
Log message: Remove BROKEN_IN variable. It was no maintained, and there was no defined workflow for setting it, removing it, or removing packages depending on it. |
| 2009-06-14 19:51:11 by Joerg Sonnenberger | Files touched by this commit (120) |
Log message: Remove @dirrm entries from PLISTs |
| 2007-03-07 18:31:23 by Joerg Sonnenberger | Files touched by this commit (3) |
Log message: Sync PLIST and build instructions: force it to believe that texi2dvi and texi2html exist, so that configure believes that the documentation is wanted. Afterwards just patch the Makefile to not really use those as intended according. |
| 2007-01-31 01:04:13 by Thomas Klausner | Files touched by this commit (36) |
Log message: Mark as BROKEN_IN pkgsrc-2006Q4, based on ftp://asim.lip6.fr/outgoing/packages/i386/3.1/20070114.1132/broken.html (latest 3.1/i386 bulk build of 2006Q4). Feel free to fix them... |
| 2006-09-10 04:52:26 by OBATA Akio | Files touched by this commit (1) |
Log message: pkglint says, INFO_FILES should be set to YES or yes. |
| 2006-09-10 04:48:35 by OBATA Akio | Files touched by this commit (1) |
Log message: Update MASTER_SITES. |
| 2006-06-16 18:17:02 by Johnny C. Lam | Files touched by this commit (1) |
Log message: A package that installs info files should define INFO_FILES in the package Makefile. |
| 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: