Hello,
First of all, happy new year :)
Intel oneAPI tbb (formerly known as Intel tbb) 2021.1 has been released and
has deprecated several interfaces over tbb 2020.
See:
https://software.intel.com/content/www/us/en/develop/articles/intel-oneapi-threading-building-blocks-release-notes.html
and:
https://software.intel.com/content/www/us/en/develop/articles/tbb-revamp.html
As a consequence, I cannot update devel/tbb anymore as most of our dependent
ports do *not* build with that new version, that includes:
Portname: Maintainer:
- ---
misc/openvdb y...@freebsd.org
misc/dartsim y...@freebsd.org
misc/ngraph y...@freebsd.org
databases/tiledb sunp...@freebsd.org
graphics/py-opencvtcber...@freebsd.org
graphics/opencv-java tcber...@freebsd.org
graphics/instant-meshes greg@unrelenting.technology
graphics/mirtky...@freebsd.org
graphics/opensubdiv free...@shaneware.biz
graphics/blender free...@shaneware.biz
graphics/opencv tcber...@freebsd.org
graphics/opencv-core tcber...@freebsd.org
graphics/oidn y...@freebsd.org
devel/py-numbad...@dal.ca
devel/ikosy...@freebsd.org
science/pagmo2y...@freebsd.org
science/madness y...@freebsd.org
www/osrm-backend free...@mosedal.net
archivers/par2cmdline-tbb marty...@freebsd.org
cad/opencascade thie...@freebsd.org
cad/PrusaSlicer teodorsig...@gmail.com
math/suitesparse fort...@freebsd.org
math/saga rhur...@freebsd.org
math/dune-pdelab y...@freebsd.org
math/openturnsy...@freebsd.org
math/curv y...@freebsd.org
The following ports seem to build correctly :
Portname: Maintainer:
- ---
math/dune-gridy...@freebsd.org
math/dune-common y...@freebsd.org
math/dune-uggrid y...@freebsd.org
math/dune-geometryy...@freebsd.org
biology/bowtie2 j...@freebsd.org
graphics/openimageio free...@shaneware.biz
graphics/embree da...@freebsd.org
math/deal.ii y...@freebsd.org
See: http://box.martymac.org/FreeBSD-Packages/build.html?
mastername=FBSD122amd64-default&build=2021-01-07_12h17m40s for more details.
To be able to smoothly introduce onetbb 2021 into the ports tree and let
maintainers migrate to that new version, here is my plan :
- leave devel/tbb in place and introduce a new port: devel/onetbb
- add a PKGNAMESUFFIX to devel/tbb to 'freeze' its version and modify
description to indicate the 'legacy' status of the port
- design devel/onetbb to install files in dedicated subdirs so that it will
not CONFLICT with current devel/tbb (needed during migration phase)
- provide a pkgconf file that will be used by dependencies to locate those
files and include/link options easily
- [let maintainers migrate their ports to that new version]
- at some time (?), mark devel/tbb as DEPRECATED with an EXPIRATION_DATE and
do the same for remaining (non-updated) deps
I would originally have preferred to do the opposite : i.e. move files from
devel/tbb to a dedicated subdir and let devel/onetbb install files to the
default PREFIX, but that would imply modifying each dependency myself, which
is something I won't have time to do (and each port's MAINTAINER is probably
the best person do do that). Doing it that way will also incite MAINTAINERs to
use the pkgconf file whenever possible to detect onetbb, wich will introduce
more flexibility for future updates.
Any comment on this ?
Best regards,
--
Ganael LAPLANCHE
http://www.martymac.org | http://contribs.martymac.org
FreeBSD: martymac , http://www.FreeBSD.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
