Navigation:
Browse pkgsrc
(this page)| 2014-05-09 09:37:28 by Thomas Klausner | Files touched by this commit (553) |
Log message: Mark packages that are not ready for python-3.3 also not ready for 3.4, until proven otherwise. |
| 2014-01-20 16:46:53 by Thomas Klausner | Files touched by this commit (2) |
Log message: Convert to distutils.mk. Mark as not for python-3.x. Bump PKGREVISION. |
| 2012-10-08 15:25:17 by Aleksej Saushev | Files touched by this commit (62) |
Log message: Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days. |
| 2012-10-04 09:02:41 by Thomas Klausner | Files touched by this commit (1) |
Log message: Remove unnecessary python restriction (to all supported versions). |
2011-04-13 16:47:18 by Matthias Drochner | Files touched by this commit (3) |  |
Log message: update to 0.7 too many changes to list here, see the release notes |
| 2009-06-14 19:35:57 by Joerg Sonnenberger | Files touched by this commit (52) |
Log message: Remove @dirrm entries from PLISTs |
| 2008-06-12 04:14:58 by Joerg Sonnenberger | Files touched by this commit (1134) |
Log message: Add DESTDIR support. |
| 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. |
| 2006-05-04 18:58:05 by Matthias Drochner | Files touched by this commit (8) | |
Log message: update MyHDL to 0.5.1 There is no usable changelog; I've found one real bug closed in the tracker: A verilog '>>>' is generated as appropriate for signed numbers. |
| 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: