Error: mapserver-7.4.0/fake-amd64/usr/local/lib/python3.7/site-packages/mapscript-7.4.0-py3.7.egg-info/PKG-INFO does not exist
Error: mapserver-7.4.0/fake-amd64/usr/local/lib/python3.7/site-packages/mapscript-7.4.0-py3.7.egg-info/SOURCES.txt does not exist
Error: mapserver-7.4.0/fake-amd64/usr/local/lib/python3.7/site-packages/mapscript-7.4.0-py3.7.egg-info/dependency_links.txt does not exist
Error: mapserver-7.4.0/fake-amd64/usr/local/lib/python3.7/site-packages/mapscript-7.4.0-py3.7.egg-info/top_level.txt does not exist
Error: mapserver-7.4.0/fake-amd64/usr/local/lib/python3.7/site-packages/mapscript/__init__.py does not exist
etc.
- Fix RUN_DEPENDS while here (-perl, -php etc... don't need python)
note that some features are broken since the update to proj 6, as
upstream QGIS only plans full support in 3.8 due in a month, but failed
to properly state so and prevent building against proj 6.
> Please note that if you use MySQL as a database, the configuration file
> has to be changed manually for this update, but MySQL is not the default
> database.
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
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@
appropriate in various devel/proj consumers to fix build with upcoming
proj 6 update, which will be commited in a month or so.
Thx to https://github.com/OSGeo/proj.4/wiki/proj.h-adoption-status for
linking the various upstream issues about it.
lang/python/python.port.mk revision 1.102 and 1.103 added
MODPY_TEST_LOCALE and MODPY_PYTEST respectively, nicely wrapping up the
usual pytest dance.
This removes hand-rolled do-tests from all 70 ports by setting
MODPY_PYTEST=Yes and MODPY_TEST_LOCALE as well as HOME=${WRKDIR} to TESTENV
as needed.
From Kurt Mosiejczuk <kurt at cranky dot work>, thanks!
OK sthen
environment, which will reduce complexity in java.port.mk when jdk 11 is
added. direction agreed with kurt@.
- switch all MODJAVA_VER to at least 1.8 (we don't currently have any
version earlier than this anyway).
- drop MODJAVA_JRERUN, the separate jre package will be going away with
jdk 11.
- bump changed ports