pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2019-09-02	Changed PYTHON_VERSIONS_INCOMPATIBLE to PYTHON_VERSIONS_ACCEPTED; needed for ↵	adam	1	-2/+2
	future Python 3.8
2019-04-26	fix some whitespace, mostly introduced in the previous	maya	1	-2/+2
	python 3.4 / 3.5 removal commit.
2019-04-26	Omit mentions of python 34 and 35, after those were removed.	maya	1	-2/+2
	- Includes some whitespace changes, to be handled in a separate commit.
2018-07-03	extend PYTHON_VERSIONS_ for Python 3.7	adam	1	-2/+2

2017-01-01	Add python-3.6 to incompatible versions.	wiz	1	-2/+2

2016-07-09	Remove python33: adapt all packages that refer to it.	wiz	1	-2/+2

2016-06-08	Switch to MASTER_SITES_PYPI.	wiz	1	-2/+2

2015-12-05	Extend PYTHON_VERSIONS_INCOMPATIBLE to 35	adam	1	-2/+2

2015-11-03	Add SHA512 digests for distfiles for math category	agc	1	-1/+2
	Problems found locating distfiles: Package dfftpack: missing distfile dfftpack-20001209.tar.gz Package eispack: missing distfile eispack-20001130.tar.gz Package fftpack: missing distfile fftpack-20001130.tar.gz Package linpack: missing distfile linpack-20010510.tar.gz Package minpack: missing distfile minpack-20001130.tar.gz Package odepack: missing distfile odepack-20001130.tar.gz Package py-networkx: missing distfile networkx-1.10.tar.gz Package py-sympy: missing distfile sympy-0.7.6.1.tar.gz Package quadpack: missing distfile quadpack-20001130.tar.gz 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-05-09	Mark packages that are not ready for python-3.3 also not ready for 3.4,	wiz	1	-2/+2
	until proven otherwise.
2014-01-25	Update HOMEPAGE. Mark as not ready for python-3.x.	wiz	1	-3/+3

2012-09-11	"user-destdir" is default these days	asau	1	-3/+1

2011-10-31	This package has no contents to buildlink.	obache	1	-15/+0

2011-02-28	Reset maintainer for retired developers.	wiz	1	-2/+2

2010-08-10	update to 0.7.2 which gives it a MASTER_SITE and a distfile again,	drochner	2	-8/+7
	I don't know of other changes from Kamel Derouiche per PR pkg/43735
2009-03-20	Simply and speed up buildlink3.mk files and processing.	joerg	1	-13/+6
	This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20	Include pyversion.mk include the protected part of the buildlink3.mk	joerg	1	-3/+3
	files, not over and over again.
2008-09-02	MASTER_SITES is not available now.	obache	1	-3/+3
	Noticed by Zafer Aydogan via private mail. Also update HOMPEGE, and add commented out SourceForge as MASTER_SITES, it only have newer version.
2008-06-12	Add DESTDIR support.	joerg	1	-1/+3

2006-07-08	Change the format of BUILDLINK_ORDER to contain depth information as well,	jlam	1	-2/+2
	and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-08	Track information in a new variable BUILDLINK_ORDER that informs us	jlam	1	-1/+2
	of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2006-04-12	Aligned the last line of the buildlink3.mk files with the first line, so	rillig	1	-2/+2
	that they look nicer.
2006-04-06	Over 1200 files touched but no revisions bumped :)	reed	1	-3/+3
	RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-02-05	Recursive revision bump / recommended bump for gettext ABI change.	joerg	2	-2/+4

2005-05-23	Removed trailing white-space.	rillig	1	-2/+2

2005-04-11	Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.	tv	1	-2/+1

2005-02-23	Add RMD160 digests in addition to SHA1 ones.	agc	1	-1/+2

2004-08-13	Add/use buildlink3.mk files.	recht	1	-0/+20

2004-06-27	update to fpconst-0.7.0	recht	2	-7/+7
	The primary purpose of this release is to correct problems on big-endian 64 bit platforms. It also introduces some test code to verify that the functions and constants work properly.
2004-04-24	Convert to buildlink3.	snj	1	-2/+2

2003-12-24	initial import of py-fpconst-0.6.0	recht	4	-0/+34
	This python module implements constants and functions for working with IEEE754 double-precision special values. It provides constants for Not-a-Number (NaN), Positive Infinity (Inf), and Negative Infinity (-Inf), as well as functions to test for these values. The code is implemented in pure python by taking advantage of the 'struct' standard module. Care has been taken to generate proper results on both big-endian and little-endian machines. Some efficiency could be gained by translating the core routines into C.