Date: Sat, 9 Jan 2021 19:19:24 +1030 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: Ganael Laplanche <ganael.laplanche@martymac.org>, freebsd-ports@freebsd.org Subject: Re: Updating devel/tbb - Introducing devel/onetbb Message-ID: <e18d9a95-d3ce-d578-66f4-0a06eac54d26@ShaneWare.Biz> In-Reply-To: <1939173.4WAli8B44Z@home.martymac.org> References: <1939173.4WAli8B44Z@home.martymac.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/1/21 9:51 pm, Ganael Laplanche wrote: > - leave devel/tbb in place and introduce a new port: devel/onetbb While I would generally support moving the old libs to a new portname, the fact that the project has renamed itself makes this acceptable. > - 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 The expected result is to have onetbb as the only option in the future, you should leave the new port to use a standard install and only if there is a need for it, alter the old port to co-install, you could get lucky and not have anyone that wants both versions installed. Use bugs.freebsd to manage the update, start with submitting onetbb, and add conflicts with tbb. If dependent ports don't update and people want both installed, submit changes to allow tbb to co-install and have depends on bugs for each port that breaks so they get updated when the tbb changes get committed. The blender port uses seven of the other ports (with options on), with three others being slaves of one, so I expect that means a third of the ports will need to be updated together, as I doubt they will work together if they link to different tbb libs. > - add a PKGNAMESUFFIX to devel/tbb to 'freeze' its version and modify > description to indicate the 'legacy' status of the port I don't see a need to make these changes to the existing port. Maybe adding a note in the pkg-descr could make people aware of the new port. > - [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 As long as the existing tbb library compiles, it can stay as it is. Once maintaining the old port to build with new compilers/systems becomes a chore, then mark tbb and deps as deprecated and give them six months to update or be deleted. If all the deps get updated before then, the old tbb port can just be deleted. If a port or two wants to stay with the old tbb, then let them maintain the tbb port. -- FreeBSD - the place to B...Software Developing Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e18d9a95-d3ce-d578-66f4-0a06eac54d26>