[Bug 259456] www/mitmproxy: 7.0.2 fails to run: pkg_resources.DistributionNotFound: The 'zstandard<0.16,>=0.11' distribution was not found

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 27 Oct 2021 09:00:57 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259456

--- Comment #3 from p5B2E9A8F@t-online.de ---
At least to me it makes almost none sense pinning maximum versions of
dependencies. This practice leads to frequently broken ports, which *must not*
be our primary goal in a dynamic environment of dependencies and using
dependencies whenever possible.

Our goal *should* be maintaining ports with the most little efforts possible as
we have already a huge workload.

Pinning maximum versions makes sense if it is already known that a coming
version of a dependency will break something. The fear that it might always be
possible is not a sufficient reason. At some places it has become a
questionable practise instead.

It *should not* need to be mentioned that repairing broken ports have priority
over delaying, waiting for something, or following policies that tend to mount
problems.  

It is a known problem with Python apps running frequently in dependency
failures. This has become to such a plague that it has become an almost general
recommendation using virtual environments. There is a general need to discuss
that development affecting the large number of FreeBSD-Python-ports having to
be maintained. 

The www/privoxy port is a general example for breaking frequently and it has a
history being broken even for months. I'm *not* pointing to the port-maintainer
here. It is a phenomenon that needs to be addressed in a more general way for
maintaining the ports.

-- 
You are receiving this mail because:
You are on the CC list for the bug.