[Bug 240578] science/py-tensorflow: Fix dependencies, Mark Un'BROKEN

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240578

--- Comment #7 from Klaus Aehlig <aehlig at linta.de> ---
> We need to find a way to make these fetch-during-build issues resilient to bazel/other dependency updates

Concerning change of dependencies by updates of bazel: bazel uses most of the
embedded rules to build itself; so, in order to make bazel packagable, the
bazel source archive contains a directory derived/distdir with all the source
archives that otherwise would have to be fetched from the network. The precise
definition can be found at
https://github.com/bazelbuild/bazel/blob/6118004e0db99820f1b6eb15d7901987c1f5481f/WORKSPACE#L116
What we could do, is to make it part of the install target of devel/bazel to
install that directory, e.g., under ${DATADIR}/distfiles so that
science/py-tensorflow could add 'build
--distdir=%%LOCALBASE%%/share/bazel/distfiles' to files/bazelrc (the --distdir
option is cummulative) and would only have to care about the dependencies
coming from the tensorflow sources themselves.

However, that would only solve part of the problem, as bazel is still
developping fast with one release per month. As of bazel 1.0.0 (comming soon,
and I already have a draft port for it, see
https://github.com/bazelbuild/bazel/issues/8573) at least incompatible changes
should only come with every major release, currently expected to come every 3
months (bazel 1.0.0 itself will also bring _a lot_ of incompatible changes).
I'm willing to maintain ports for older versions of bazel, but we probably
should have a guideline which old versions to keep, as adding a new bazel port
every quarter might clutter the ports tree to much unless we have a good policy
on when to remove the ports for the older versions.

-- 
You are receiving this mail because:
You are the assignee for the bug.