Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 87d92307 | 2019-07-13 06:48:16 | update python 3 to 3.7.4. tested in a bulk build on amd64 by naddy@ (thanks). | ||
| 3318ced0 | 2019-07-12 20:46:54 | replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes | ||
| 9765018e | 2019-06-24 14:25:54 | change -S MODPY_ABI3SO to -I MODPY_ABI3SO in python.port.mk's UPDATE_PLIST_ARGS; the former is incorrect as the ".abi3" string is in the middle of the path, not the end. ok espie@ jca@ | ||
| ebf751b9 | 2019-05-20 22:15:00 | Update gettext to 0.20.1. Follow the upstream recommendations for packagers and switch to multi-packages: devel/gettext -> devel/gettext,-runtime devel/gettext-tools -> devel/gettext,-tools (new) devel/gettext,-textstyle | ||
| 85103780 | 2019-05-18 18:56:45 | make use of new update-plist options (make sure your update-plist is current!) | ||
| cc56f40f | 2019-05-18 00:33:52 | check that FLAVORS is defined before using it in .if; problem with "make plist" following prior commit reported by juanfra@ with devel/mercurial. | ||
| 70e3a42d | 2019-05-17 13:27:03 | It's well-known that update-plist has a hard time on py2/py3 ports when run outside the py3 flavor, so gently remind the porters. okay sthen@ | ||
| 1bc740e8 | 2019-05-16 18:15:40 | set MODPY_TESTDEP dependent to NO_TEST. it will avoid populate TEST_DEPENDS when the port has explicitly declared there is no test. ok kmos@ | ||
| c45cd79f | 2019-05-15 12:04:34 | Add RUN_DEPENDS to TEST_DEPENDS automatically for ports using the lang/python port module. I've not yet come up with a port that would not need this and one can always set MODPY_TESTDEP to "no" to prevent the module from touching TEST_DEPENDS. Idea from afresh1 who pointed out the cpan module already does this. aja "I support this move." OK sthen@ | ||
| 228a5f9e | 2019-05-10 12:01:55 | fix @pkgpath markers; - there was never a lang/python3/3.6 (@pkgpath marker for this is present in current 3.6 plists), python3/3.x was only used for 3.2, so remove these. - they should probably have originally used "@pkgpath lang/python/3.5" to trigger updates from 3.5 when 3.5 was removed, but no point adding those to 3.6 now that 3.7 is the default version. so add @pkgpath lang/python/3.5 markers in 3.7 PLISTs, fixing the upgrade path if old versions were present (there was previously nothing to trigger 3.5 being removed/updated so stray packages would be left around). problem reported by Laurie Tratt |