Date: Sun, 15 Sep 2019 06:33:45 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 240578] science/py-tensorflow: Fix dependencies, Mark Un'BROKEN Message-ID: <bug-240578-7788-lBdetK1Aex@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-240578-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-240578-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240578 --- Comment #7 from Klaus Aehlig <aehlig@linta.de> --- > We need to find a way to make these fetch-during-build issues resilient t= o bazel/other dependency updates Concerning change of dependencies by updates of bazel: bazel uses most of t= he embedded rules to build itself; so, in order to make bazel packagable, the bazel source archive contains a directory derived/distdir with all the sour= ce archives that otherwise would have to be fetched from the network. The prec= ise definition can be found at https://github.com/bazelbuild/bazel/blob/6118004e0db99820f1b6eb15d7901987c1= f5481f/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=3D%%LOCALBASE%%/share/bazel/distfiles' to files/bazelrc (the --di= stdir 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 soo= n, and I already have a draft port for it, see https://github.com/bazelbuild/bazel/issues/8573) at least incompatible chan= ges 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 p= ort every quarter might clutter the ports tree to much unless we have a good po= licy on when to remove the ports for the older versions. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240578-7788-lBdetK1Aex>