[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc-2014Q2 2012-05-07T01:53:12Z 2012-05-07T01:53:12Z dholland dholland@pkgsrc.org 2012-05-07T01:53:12Z urn:sha1:0bcdacfbcf0a1f7f4455399808295e6e6f7e01bc It turns out there were a lot of these. 2009-03-20T19:23:50Z joerg joerg@pkgsrc.org 2009-03-20T19:23:50Z urn:sha1:2d1ba244e90207d03eef397a99aa4091baeec5b3 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@pkgsrc.org 2009-03-20T17:30:09Z urn:sha1:0d0e90a320db4ce34595ef02e4914c67eb4505a6 files, not over and over again. 2006-07-08T23:10:35Z jlam jlam@pkgsrc.org 2006-07-08T23:10:35Z urn:sha1:c16221a4db5db247e9ecea04d817821955982042 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@pkgsrc.org 2006-07-08T22:38:58Z urn:sha1:9430e4930752307717c0058ee21f02a3ea56b0ad of the order in which buildlink3.mk files are (recursively) included by a package Makefile. 2006-04-12T10:26:59Z rillig rillig@pkgsrc.org 2006-04-12T10:26:59Z urn:sha1:96fc47c14f1c212bb44b3fea33a48ff9851c6bdd that they look nicer. 2006-04-06T06:21:32Z reed reed@pkgsrc.org 2006-04-06T06:21:32Z urn:sha1:5abef9be142e900cceace758044a1b2ee493daf3 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@pkgsrc.org 2006-02-05T23:08:03Z urn:sha1:5911def8168a758ff36655bdfb061b58eb52ff1c 2005-02-09T12:16:02Z markd markd@pkgsrc.org 2005-02-09T12:16:02Z urn:sha1:4852d16c98c20e004165d4634354d11156f5db35 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@pkgsrc.org 2004-04-22T15:14:59Z urn:sha1:97e5756142ac4bed61d24b795e42664972542e48