Commit graph

9 commits

Author SHA1 Message Date
nia
28c1048bad misc: Replace RMD160 checksums with BLAKE2s checksums
All checksums have been double-checked against existing RMD160 and
SHA512 hashes

The following distfiles could not be fetched (possibly fetched
conditionally?):

./misc/libreoffice/distinfo libreoffice/harfbuzz-2.6.4.tar.xz
2021-10-26 10:58:55 +00:00
nia
60e6853f70 misc: Remove SHA1 hashes for distfiles 2021-10-07 14:35:11 +00:00
agc
23064a80b9 Add SHA512 digests for distfiles for misc category
Problems found locating distfiles:
	Package colorls: missing distfile ls.tar.gz
	Package molden: missing distfile molden-4.6/molden4.6.tar.gz
	Package softmaker-office-demo: missing distfile ofl06trial.tgz

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.
2015-11-03 23:49:31 +00:00
asau
9912a3809d Drop PKG_DESTDIR_SUPPORT setting, "user-destdir" is default these days. 2012-10-08 09:57:15 +00:00
joerg
62d1ba2bac Remove @dirrm entries from PLISTs 2009-06-14 18:03:28 +00:00
jlam
39843c2c61 Mechanical changes to add DESTDIR support to packages that install
their files via a custom do-install target.
2008-03-04 19:21:10 +00:00
jlam
9c8b5ede43 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.
2006-03-04 21:28:51 +00:00
joerg
5911def816 Recursive revision bump / recommended bump for gettext ABI change. 2006-02-05 23:08:03 +00:00
agc
5f1c542edc Initial import of a list of UK national postcodes into the Packages
Collection. The list is a five-field CSV file.

	Free list of UK postcodes

	The list is formatted as plain text, with each record on a separate
	line.  Each record consists of five fields, each field being separated
	by a comma.  You should be able to import this data into most
	applications that support "comma separated variables".  The five
	fields are:

	   1. First part of the UK postcode (area code)
	   2. x-coordinate (metres)
	   3. y-coordinate (metres)
	   4. Latitude
	   5. Longitude
2005-05-26 08:58:43 +00:00