Navigation:
Browse pkgsrc
(this page)| 2010-02-14 22:36:26 by Joerg Sonnenberger | Files touched by this commit (3) |
Log message: DESTDIR support |
| 2010-01-18 10:59:46 by Thomas Klausner | Files touched by this commit (938) |
Log message: Second try at jpeg-8 recursive PKGREVISION bump. |
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-06-14 21:10:38 by Joerg Sonnenberger | Files touched by this commit (30) |
Log message: Convert @exec/@unexec to @pkgdir or drop it. |
| 2009-06-14 19:57:02 by Joerg Sonnenberger | Files touched by this commit (215) |
Log message: Remove @dirrm entries from PLISTs |
| 2006-12-15 21:33:06 by Joerg Sonnenberger | Files touched by this commit (236) |
Log message: Mechanically replace all includes of buildlink3.mk of the following packages with the modular Xorg equivalent. Those are falling back to the old location by default, so this commmit doesn't change dependencies. graphics/xpm ==> x11/libXpm fonts/Xft2 ==> x11/libXft x11/Xfixes ==> x11/libXfixes x11/xcursor ==> x11/libXcursor x11/Xrender ==> x11/libXrender x11/Xrandr ==> libXrandr |
| 2006-08-03 03:00:00 by Krister Walfridsson | Files touched by this commit (3) |
Log message: Fix "static declaration follows non-static" and "extra \ qualification" errors that prevented build with gcc 4.1. |
| 2006-04-28 18:23:55 by Joerg Sonnenberger | Files touched by this commit (5) |
Log message: Fix C++ for GCC 3.4+. Always link with pthread when linking with qt-mt. |
| 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. |
New packages: