Hi Michael,
I went through the list of missing dependencies.
aws-*: I'm not interested in them. In the past I just (manually)
filtered out all the code associated with aws functionalities.
Most of them are possibly not packaged yet.
abseil-cpp: this is a tricky one. Similar to facebook/folly. It does
not guarantee a stable ABI. Once the system-provided abseil
breaks the tensorflow, we have to embed one.
Anyway it's present in our archive: libabsl-dev but I don't
know whether tensorflow builds against it.
re2: already present in archive. I guess there is no reason to embed it.
boringssl: maybe a simple string replacement s/boring/open/g will just work?
farmhash: in archive, and I'm the uploader. Ping me if it needs to be updated.
eigen: sometimes TF relies on new features that debian's libeigen3-dev
does not provide. In that case we have to use an embedded
tarball again.
highwayhash: in archive, and I'm the uploader.
fft2d: TF uses merely 1 source file from this project for merely
one OP/Kernel. Just keep it embedded.
The last upstream update was ~10 yrs ago (IIRC).
On Mon, Aug 31, 2020 at 05:32:56PM +0200, Michael R. Crusoe wrote:
> Hey Mo, we have some unpackaged dependencies. Currently TensorFlow can be built
> using code copies, but obviously that isn't a great plan. Here are the current
> code copies: https://github.com/meteorcloudy/tensorflow/tree/r2.2-debian/debian
> /dist
>
> If you want to help out you can use the bazel-bootstrap and
> libcheck-framework-java binary packages from https://people.debian.org/~olek/
> packages/
Great! Thanks for the hint.