Navigation:
Browse pkgsrc
(this page)| 2021-10-26 12:06:54 by Nia Alarie | Files touched by this commit (150) |
Log message: converters: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes |
| 2021-10-07 15:29:13 by Nia Alarie | Files touched by this commit (150) |
Log message: converters: Remove SHA1 hashes for distfiles |
| 2015-11-03 02:43:56 by Alistair G. Crooks | Files touched by this commit (120) |
Log message: Add SHA512 digests for distfiles for converters category Problems found with existing distfile: distfiles/libiconv-1.13-cp932.patch.gz No changes made to the libiconv distinfo file. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail. |
| 2014-02-08 13:44:05 by Sebastian Wiedenroth | Files touched by this commit (2) |
Log message: fix build on SunOS (included paths.h) |
| 2012-10-03 02:20:19 by Aleksej Saushev | Files touched by this commit (97) |
Log message: Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. |
| 2010-11-02 10:36:03 by Thomas Klausner | Files touched by this commit (1) |
Log message: Set LICENSE. |
| 2010-01-29 17:54:40 by Joerg Sonnenberger | Files touched by this commit (1) |
Log message: DESTDIR support |
| 2008-06-01 23:49:56 by David A. Holland | Files touched by this commit (3) |
Log message: Fix insecure-temporary-files, as reported in Debian bug 480972. PKGREVISION++. |
| 2007-02-22 20:27:30 by Thomas Klausner | Files touched by this commit (721) |
Log message: Whitespace cleanup, courtesy of pkglint. Patch provided by Sergey Svishchev in private mail. |
| 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: