Commit graph

24 commits

Author SHA1 Message Date
joerg
2d1ba244e9 Simply and speed up buildlink3.mk files and processing.
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 19:23:50 +00:00
joerg
0d0e90a320 Include pyversion.mk include the protected part of the buildlink3.mk
files, not over and over again.
2009-03-20 17:30:09 +00:00
joerg
ba171a91fa Add DESTDIR support. 2008-06-12 02:14:13 +00:00
joerg
a77e7015fe Update PYTHON_VERSIONS_COMPATIBLE
- assume that Python 2.4 and 2.5 are compatible and allow checking for
fallout.
- remove PYTHON_VERSIONS_COMPATIBLE that are obsoleted by the 2.3+
default. Modify the others to deal with the removals.
2008-04-25 20:39:06 +00:00
jlam
841dfa0e7a Convert to use PLIST_VARS instead of manually passing "@comment "
through PLIST_SUBST to the plist module.
2008-04-12 22:42:57 +00:00
drochner
64d7e6f72a update to 1.5.2
This is a very modest release which primarily consists of bug fixes to
numarray's implementation of the numpy array interface.
2006-10-17 14:25:43 +00:00
jlam
c16221a4db Change the format of BUILDLINK_ORDER to contain depth information as well,
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 23:10:35 +00:00
jlam
9430e49307 Track information in a new variable BUILDLINK_ORDER that informs us
of the order in which buildlink3.mk files are (recursively) included
by a package Makefile.
2006-07-08 22:38:58 +00:00
rillig
96fc47c14f Aligned the last line of the buildlink3.mk files with the first line, so
that they look nicer.
2006-04-12 10:26:59 +00:00
reed
5abef9be14 Over 1200 files touched but no revisions bumped :)
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-04-06 06:21:32 +00:00
minskim
cebefd121c Let the package find BLAS routines on Mac OS X. This makes the package build
on Darwin.
2006-03-08 17:21:34 +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
drochner
e1f01d3eec update to 1.5.1
changes:
-fix a NumArray Operator Optimization Bug
-Better NumPy dtype Support.
-more bugfixes
2006-02-15 16:41:04 +00:00
drochner
5da3bad38a update to 1.5
changes:
-better interoperability with py-Numeric and scipy (uses "scipy newcore")
-bugfixes
-speed improvements
2006-02-07 13:28:08 +00:00
joerg
5911def816 Recursive revision bump / recommended bump for gettext ABI change. 2006-02-05 23:08:03 +00:00
drochner
d407f9bd85 remove sitecustomize - this doesn't belong here
should fix bulk-build error
2005-10-25 11:18:52 +00:00
drochner
32e407bce8 update to 1.3.3
changes:
-many bugfixes
-code cleanup, speedup
2005-10-21 14:57:02 +00:00
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
agc
1e46c076aa Add RMD160 digests in addition to SHA1 ones. 2005-02-23 12:06:53 +00:00
markd
4852d16c98 Update py-numarray to version 1.1.1
Support Python 2.4

1.1.1 changes:
numarray-1.1.1 is a bugfix release to numarray-1.1. Notable bugs
fixed include memory leaks in matrixmultiply and comparison ufuncs.


1.1 changes:
I. ENHANCEMENTS

CharArray eval() sped up
Document memmap.py (memory mapping)
Unsigned int type support limited
Add kroenecker product

II. BUGS FIXED / CLOSED

max.reduce of byteswapped array
numeric compatibility byteoffset
matrixmultiply (a,b) leaves b transposed
random_array.randint exceeds boundaries
buffer not aligned on 8 byte boundary  (Windows-98 broken)
Object Array repr for >1000 elements
Invalid sequences errors
Segfault in array element deletion
Incorrect handling of overlapping assignments in Numarray
Weirdness with 'new' method
searchsorted bug and fix
randint bug fix patch
a.is_c_array() mixed int/bool results
argsort of string arrays

III. CAUTIONS

1. This release is binary incompatible with numarray-1.0.  Writers of
C-extensions which directly reference the byteoffset field of the
PyArrayObject should be aware that the data pointer is now the sum of
byteoffset and the buffer base pointer.  All C extensions which use
the numarray C-API must be recompiled.  This incompatibility was an
unfortunate consequence of the fix for "numeric compatibility
byteoffset".
2005-02-09 12:16:02 +00:00
recht
367eed19fe Build Python with thread support by default and turn the existing
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
2005-01-23 20:41:45 +00:00
recht
86865c78c3 update to 1.0
important changes:

- Ports of Numeric functions

A bunch of Numeric functions were ported to numarray in the new
libnumeric module.  To get these import from numarray.numeric.  Most
notable among these are put, putmask, take, argmin, and argmax.  Also
added were sort, argsort, concatenate, repeat and resize.  These are
independent ports/implementations in C done for the purpose of best
Numeric compatibility and small array performance.  The numarray
versions, which handle additional cases, still exist and are the
default in numarray proper.

- Faster matrix multiply

The setup for numarray's matrix multiply was moved into C-code.  This
makes it faster for small matrices.

- bug fixes

For a complete list of changes see:
http://sourceforge.net/project/shownotes.php?release_id=250453
2004-07-09 15:50:25 +00:00
drochner
97e5756142 add one 2004-04-22 15:14:59 +00:00
drochner
a720ec32ed import the numarray-0.9 Python extension - a reimplemantation of
py-Numeric
2004-04-21 20:46:54 +00:00