I just noticed this issue and I think it is an acceptable way to
create new bazel5
port if TensorFlow really needs it. I added the TensorFlow port so I am
happy to work with you to fix it.
On Fri, Dec 15, 2017 at 10:06 AM, Jov <am...@amutu.com> wrote:
> I tried to fix and update the py-tensorflow last week but failed because
> the bazel and tensorflow upstream seem heavily development and a lot of
> things changed. My time for the ports work is limited so I will give up
> this port. Anyone can take it and I am fine to answer any question.
> The easiest fixing is to create a new port bazel5 with 0.5.3 as version and
> change the tensorflow depend on this new port.
> 2017-12-15 9:21 GMT+08:00 Jason Bacon <bacon4...@gmail.com>:
> > Hi Jov,
> > Are you aware that your py-tensorflow port is marked BROKEN?
> > Thanks for porting this, BTW. We have researchers interested in it and
> > use FreeBSD quite a bit here.
> > Cheers,
> > Jason
> > --
> > Earth is a beta site.
> firstname.lastname@example.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Li-Wen Hsu <lw...@freebsd.org>
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"