Comments regarding tensorflow_2.0.0-1_amd64.changes

[M. Zhou]

The fact is that if embedded code copies were prohibited,
I can list a couple of source packages to purge from the archive.
And that would demotivate more contributors.

The point is that, sometimes disentangling the embedded code
from the upstream source can cost much greater amount of
time and energy from the maintainer. That's somehow harsh
to the contributors. Embedded code copies may have different
and interesting reasons.

We all like to handle clean and elegant upstreams. But the
fact is that there are always an amount of unelegant upstreams
such as Google (bazel, tensorflow, abseil-cpp), Facebook (pytorch,
folly) which are quite unfriendly to distributions.

The contributor has only two choices at low cost: 1) totally
ignore this piece of software even if it seemed useful 2) doing
something not quite elegant such as embedding a convenient copy.

Speaking of policy, "should" is a good trade-off that I agree with.

On Tue, 3 Mar 2020 at 04:04, Sean Whitton <spwhitton at spwhitton.name> wrote:

> Hello Mo,
>
> On Tue 03 Mar 2020 at 08:23AM +08, M. Zhou wrote:
>
> > Eigen3 is used in the core math part of tensorflow. I have limited energy
> > to patch these parts from time to time whenever eigen3 gets updated. I
> > dislike introducing burden to myself.
> >
> > Please reject it so I can get rid of this burden permanently.
>
> Rejected per your request, but from my point of view this discussion is
> not over -- Policy 4.13 says that packages *should* not use convenience
> copies of code, not that they *must* not.
>
> Thank you for all your work on uploading useful ML packages.
>
> --
> Sean Whitton
>


-- 
Best,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20200303/22eaf729/attachment-0001.html>