pkgsrc/math/quadpack, branch trunk [no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk 2021-10-26T10:55:21Z math: Replace RMD160 checksums with BLAKE2s checksums 2021-10-26T10:55:21Z nia nia@pkgsrc.org 2021-10-26T10:55:21Z urn:sha1:35050bad02b57ed8ca4a6430799b6800b9846072 All checksums have been double-checked against existing RMD160 and SHA512 hashes math: Remove SHA1 hashes for distfiles 2021-10-07T14:27:43Z nia nia@pkgsrc.org 2021-10-07T14:27:43Z urn:sha1:a4dc7f45228012c1f678c7bbf0d0693040642bf6 Extend SHA512 checksums to various files I have on my local distfile 2017-03-23T17:06:45Z joerg joerg@pkgsrc.org 2017-03-23T17:06:45Z urn:sha1:d614958d932c30b665a2140573c478122cc323b8 mirror. "user-destdir" is default these days 2012-09-11T23:04:15Z asau asau@pkgsrc.org 2012-09-11T23:04:15Z urn:sha1:b0feb9f5b186a62a131121fe59db9ccdc0a844bd "fortran" -> "fortran77" except where it is clear that it isn't F77. 2010-07-30T10:36:22Z asau asau@pkgsrc.org 2010-07-30T10:36:22Z urn:sha1:8756d19398c644e5cacae9ea605bfce473f10145 "fortran" is alias of "fortran77" for now, but it will change later. Support staged installation. 2009-12-12T21:58:18Z asau asau@pkgsrc.org 2009-12-12T21:58:18Z urn:sha1:2e045c8460d0afc39f5bf02631be8fb267713c8b Follow f2c/libf2c split: bump revision of all packages 2009-12-03T13:06:51Z asau asau@pkgsrc.org 2009-12-03T13:06:51Z urn:sha1:d78ee9706fa60290d2c69af143254783ad92228a that list Fortran in used languages. Remove @dirrm entries from PLISTs 2009-06-14T18:03:28Z joerg joerg@pkgsrc.org 2009-06-14T18:03:28Z urn:sha1:24151e2b9991726fa4bcd0ace9289f45de0f325e Prepare for switching to NO_MTREE=yes. 2007-03-24T19:21:18Z joerg joerg@pkgsrc.org 2007-03-24T19:21:18Z urn:sha1:161c920c15367de281f689f6f1177c3a33e63cc6 Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no 2006-03-04T21:28:51Z jlam jlam@pkgsrc.org 2006-03-04T21:28:51Z urn:sha1:9c8b5ede437e0b7c2f7b0cdd5f8500d619968fdb 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.