Are you sure that this is the correct install location? Shouldn't it go into tensorflow2-devel and tensorflow2-lite-devel needs to depend on it?

grep '#include "tensorflow/core' -R /usr/include/tensorflow/lite/ yields quite a list of header files which are to be included but not packaged by tensorflow2{,-lite}-devel

I grepped over the include files in tensorflow2-devel and did not spot any consumer of this version.h file, thus I've decided to only include it in the lite version only. Now, you seem to have spotted more header file requirements in the lite version that will only be met by tensorflow2-devel, so this may make it more feasible to set up this dependency and include the header there. On the other hand, what's the point for the two versions being shipped separately at all, then? Or is there a common subset of headers that should go into a *devel-common package?

From all I've heard and seen about TF, it is not a software that is meant for packaging. It seems to aim at being containerized. Trying to fight this will be a recurring uphill battle. Thus, I'm wondering it we were not better off to look into a different delivery method and drop the package.

Guillaume GARDET (Guillaume_G) - over 2 years ago

target maintainer

Some packages depend on it, such as Arm NN.