2009-09-03 10:59:44 by Thomas Klausner | Files touched by this commit (5) | ![]() |
Log message: Remove boaconstructor, replaced with boa-constructor. |
2009-08-26 21:58:47 by Jens Rehsack | Files touched by this commit (1461) | ![]() |
Log message: bump revision because of graphics/jpeg update |
2009-08-25 13:57:46 by Thomas Klausner | Files touched by this commit (22) |
Log message: Get rid of now unnecessary EXTRACT_OPTS_ZIP. |
2009-06-14 19:49:18 by Joerg Sonnenberger | Files touched by this commit (454) |
Log message: Remove @dirrm entries from PLISTs |
2009-02-09 23:56:28 by Joerg Sonnenberger | Files touched by this commit (167) |
Log message: Switch to Python 2.5 as default. Bump revision of all packages that have changed runtime dependencies now. |
2008-05-26 04:13:26 by Joerg Sonnenberger | Files touched by this commit (274) |
Log message: Second round of explicit pax dependencies. As reminded by tnn@, many packages used to use ${PAX}. Use the common way of directly calling pax, it is created as tool after all. |
2008-04-25 22:39:14 by Joerg Sonnenberger | Files touched by this commit (170) |
Log message: Update PYTHON_VERSIONS_COMPATIBLE - assume that Python 2.4 and 2.5 are compatible and allow checking for fallout. - remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+ default. Modify the others to deal with the removals. |
2008-03-03 18:45:38 by Johnny C. Lam | Files touched by this commit (119) |
Log message: Mechanical changes to add DESTDIR support to packages that install their files via a custom do-install target. |
2006-04-17 15:47:02 by Thomas Klausner | Files touched by this commit (1055) | ![]() |
Log message: Bump BUILDLINK_ABI_DEPENDS.png and PKGREVISION for png-1.2.9nb2 update. |
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. |