If you have math/py-numpy installed, then build the devel/boost-python-libs port, check-plist will have the following errors: ====> Checking for pkg-plist issues (check-plist) ===> Parsing plist ===> Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: lib/libboost_numpy.a Error: Orphaned: lib/libboost_numpy.so Error: Orphaned: lib/libboost_numpy.so.%%BOOST_SHARED_LIB_VER%% One fix would be to make math/py-numpy be a dependency (presumably RUN_ or LIB_, but I haven't checked). That is a pretty heavy dependency for someone who doesn't want to install numpy. Another is to make the numpy dependency an option and force the build to not build the libboost_numpy library if that option is off (I don't know the bjam/Boost.Build magic to tell it not to build the boost_numpy lib right now).
Created attachment 190286 [details] [patch] address numpy dependency with explicit option Here is a patch to solve this problem... - fix plist for devel/boost-python{,3}-libs if math/py-numpy is installed by added NUMPY option. If off, disable building libboost_numpy [1]. If on, depend on the numpy port [2]. Default: off - matches current packages. - minor portlint appeasement PORTREVISION bump is probably not necessary since it will not change the package contents built by default. [1] There is probably a better way to force disabling the numpy build (arg to bjam?). [2] Not sure if this should also be a runtime dependency, but ldd does not indicate a dependency.
Created attachment 190695 [details] [patch] address numpy dependency with explicit option [v2] refresh patch after r461885 (flavorize)
maintainer timeout?
This is still a problem. Can someone please commit this?
Created attachment 192770 [details] [[patch] address numpy dependency with explicit option [v3] Refresh patch based on current state of boost and boost-python-lib ports. - fix plist for devel/boost-python{,3}-libs if math/py-numpy is installed by added NUMPY option. If off, disable building libboost_numpy [1]. If on, depend on the numpy port [2]. Default: off - matches current packages. - minor portlint appeasement
Option (if non-default) isn't a good approach as it'd prevent ports depending on libboost_numpy. As USE_PYTHON=flavors is incompatible with custom-defined FLAVORS libboost_numpy probably needs to move into a slave port or maybe wait for subpackaging support i.e., one port produces multiple packages.
A commit references this bug: Author: jbeich Date: Sat Jun 8 03:13:23 UTC 2019 New revision: 503700 URL: https://svnweb.freebsd.org/changeset/ports/503700 Log: devel/boost-python-libs: add NumPy support numpy component is always built but runtime dependency is left out until subpackaging to avoid always pulling py-numpy. Consumers should add RUN_DEPENDS+=${PYNUMPY} instead to avoid the following: ImportError: No module named numpy.core._multiarray_umath ImportError: numpy.core._multiarray_umath failed to import PR: 225589 238130 Changes: head/devel/boost-python-libs/Makefile head/devel/boost-python-libs/pkg-plist