Navigation:
Browse pkgsrc
(this page)| 2010-07-30 12:36:34 by Aleksej Saushev | Files touched by this commit (51) |
Log message: "fortran" -> "fortran77" except where it is clear that it \ isn't F77. "fortran" is alias of "fortran77" for now, but it will \ change later. |
| 2010-02-07 19:36:33 by Zafer Aydogan | Files touched by this commit (1) |
Log message: add license. |
| 2009-12-11 03:11:52 by Aleksej Saushev | Files touched by this commit (8) |
Log message: Support staged installation. |
| 2009-12-03 14:06:56 by Aleksej Saushev | Files touched by this commit (48) |
Log message: Follow f2c/libf2c split: bump revision of all packages that list Fortran in used languages. |
| 2009-06-14 20:05:51 by Joerg Sonnenberger | Files touched by this commit (88) |
Log message: Remove @dirrm entries from PLISTs |
| 2007-11-12 00:56:53 by Thomas Klausner | Files touched by this commit (1) |
Log message: Remove fire.mpi-stuttgart.mpg.de and wauug.erols.com from MASTER_SITES, they don't resolve. From Zafer Aydogan in PR 37320. |
| 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-07-21 07:27:21 by Roland Illig | Files touched by this commit (1) |
Log message: Fixed the path to the Perl interpreter. Bumped PKGREVISION. |
| 2006-07-21 07:22:33 by Roland Illig | Files touched by this commit (1) |
Log message: Needs a C compiler. |
| 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: