pkgsrc/lang/python25, branch pkgsrc_2009Q3 [no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2009Q3 2009-09-19T09:18:53Z Fixes module names in disabled_module_list 2009-09-19T09:18:53Z obache obache 2009-09-19T09:18:53Z urn:sha1:499d9636741a115e496622b5fc2a8257685ca7eb * not "_sqlite", but "_sqlite3" * "bsddb" does not exists, probably removed/renamed before Python24 * "cjkcodes" does not exists (and should not be disabled) * missng "," afiter it * "mpz" was removed in Python24. Fix build under Mac OS X Snow Leopard. 2009-09-12T22:24:06Z tron tron 2009-09-12T22:24:06Z urn:sha1:a737a3b9206cd28b08c2742d55dd3379162596b7 remove assignments to the LIBS env var -- this should have been done 2009-09-12T17:47:17Z drochner drochner 2009-09-12T17:47:17Z urn:sha1:a30e15cdbb2c27be9c6a08e8dce8dc068079db7b earlier, but there became no-ops due to my change to db4/bl3 and thus didn't do harm. Now that part of that change was backed out they became harmful again and thus need to go. Fix a possibly long-standing issue, but also possibly fallout from the db4 2009-09-09T05:37:51Z dsainty dsainty 2009-09-09T05:37:51Z urn:sha1:aa3d5bb148003a5a10e219b9bb49b5467fc656b5 changes. The "dbm" module could fail to build correctly, erroring out with: *** WARNING: renaming "dbm" since importing it failed: build/lib.linux-i686-2.5/dbm.so: undefined symbol: dbm_firstkey In this case, the "dbm" module has accidentally linked with "databases/gdbm", which happens to be installed, but was never buildlinked in. It may be relevant that /usr/include/gdbm/ndbm.h is installed on this system. Remove the "gdbm" test from the "dbm" module configuration, leaving the "ndbm" support, and the fall-back "bdb" support (which will likely fall back to db4). Bump PKGREVISION - the package would still install, but with missing functionality. bump PKGREVs for Python pkgs, as suggested by David Sainty -- at least 2009-09-08T10:06:35Z drochner drochner 2009-09-08T10:06:35Z urn:sha1:561bdef60bb1f177e85c08aa6b685bcd9b0ebe65 on Linux one can't build some extensions against an old Python (with spurious -ldb4 linkage) anymore also sync the bl3 files of the non-default versions with python25 for consistency don't propagate the "cups" dependency, this is nut referenced by 2009-09-07T18:42:39Z drochner drochner 2009-09-07T18:42:39Z urn:sha1:39ba41cab5c8edb68238b59b9ea5a2a85e27d3c2 the exported libraries (according to the CVS log, this was only to work around spurious db4 dependencies which are hopefully fixed by my last change to db4/bl3) gdbm is in disabled_module_list, yet if it's found on the system 2009-07-24T14:50:33Z schmonz schmonz 2009-07-24T14:50:33Z urn:sha1:d85f9cd58eb5a3a51974104c53da79587137f82f the module gets built anyway. Don't do that. Remove empty PLIST.common_end. 2009-07-22T09:29:57Z wiz wiz 2009-07-22T09:29:57Z urn:sha1:3728b8eb5214ddebc715bad135ab145840b9a7fb Remove @dirrm entries from PLISTs 2009-06-14T18:03:28Z joerg joerg 2009-06-14T18:03:28Z urn:sha1:870ee431b3152f330a121f8399ba6a71540929c1 Recursive ABI depends update and PKGREVISION bump for readline-6.0 shlib 2009-05-20T00:58:05Z wiz wiz 2009-05-20T00:58:05Z urn:sha1:bce310e12c34dd199b2fb13ec720a93538f33642 major change. Reported by Robert Elz in PR 41345.