[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2015Q2 2012-05-07T01:53:12Z 2012-05-07T01:53:12Z dholland dholland 2012-05-07T01:53:12Z urn:sha1:cc1ac695ede7d3d2b8292cbd2a5325c37d1f50a1 It turns out there were a lot of these. 2009-03-20T19:23:50Z joerg joerg 2009-03-20T19:23:50Z urn:sha1:405c61d80251d8e80401aed2264d4bede218cb22 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-20T17:30:09Z joerg joerg 2009-03-20T17:30:09Z urn:sha1:572cec3939d3a28810a3297ec5ad4a5d7abb3a7e files, not over and over again. 2006-07-08T23:10:35Z jlam jlam 2006-07-08T23:10:35Z urn:sha1:b96729a13e6502c6d9d1c2912a698e23f57d3965 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-08T22:38:58Z jlam jlam 2006-07-08T22:38:58Z urn:sha1:6e7d67f4b1fea88b6cff1f00142907eca4188add of the order in which buildlink3.mk files are (recursively) included by a package Makefile. 2006-04-12T10:26:59Z rillig rillig 2006-04-12T10:26:59Z urn:sha1:f39c7a6814118271c6fbfe87140ce12d8a3146d7 that they look nicer. 2006-04-06T06:21:32Z reed reed 2006-04-06T06:21:32Z urn:sha1:3b50716541c42bd031d14157665a74004901cade 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-05T23:08:03Z joerg joerg 2006-02-05T23:08:03Z urn:sha1:93e3b9e04264b93620166058e19ea42c856505b0 2005-02-09T12:16:02Z markd markd 2005-02-09T12:16:02Z urn:sha1:d09dfe35121dfa94f7a0a32042d55403b8c96319 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". 2004-04-22T15:14:59Z drochner drochner 2004-04-22T15:14:59Z urn:sha1:6db2a50155ccd9181cc65b1009a521d9b02ee17b