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@
naddy@ and ajacoutot@, independently from each other, found that the
recent update of py-matplotlib does not build. Issue is caused by me not
noticing that matplotlib tries to download jquery-ui-1.12.1, which fails
when building in a chroot using dpb. Instead of downloading jquery-ui
use the bundled files.
REVISION is not bumped as patched file is not included in the package,
and no new files are added.
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
By default we depend on py-gtk+2 except for the python3 FLAVOR where we depend
on py-gobject3 and gtk+3. We don't want to depend on all possible toolkits for
obvious reason, so people will have to manually install py-qt4 for example to
use the qt4 toolkit.
changes triggered by a mail from Predrag Punosevac
ok daniel@ (maintainer) who may revisit this port if needed in a few days
A single test is failing, however, the test code works fine when run
outside of the test harness. I raised a bug here:
https://github.com/matplotlib/matplotlib/issues/2101
OK sthen@ and lots of input from fgs@. Thanks.
