[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1343: how does a packager find version requirements for indirect dependencies?

[Tahoe-LAFS]

#1343: how does a packager find version requirements for indirect dependencies?
----------------------------+-----------------------
     Reporter:  davidsarah  |      Owner:  somebody
         Type:  defect      |     Status:  new
     Priority:  major       |  Milestone:  undecided
    Component:  packaging   |    Version:  1.8.1
   Resolution:              |   Keywords:  docs
Launchpad Bug:              |
----------------------------+-----------------------

Comment (by exarkun):

 Tahoe-LAFS has a lot of transitive dependencies now.  If anything, this
 issue is much worse and more pressing than it was 7 years ago.  Yet there
 is still no particularly good solution.

 "Try some versions and see if they work"?  That is essentially all the
 Tahoe-LAFS project does.  "some versions" are generally "the latest
 releases of most things at the time of testing / release".

 A package could look at Tahoe-LAFS CI and see what those versions are and
 pick them.  On the other hand, a packager is almost certainly going to use
 whatever versions of the dependencies someone else has already packaged in
 the system they are packaging for.  And if the result doesn't work ...
 well, is anyone going to care?

 I think it would be great to fix this but I don't know what change is
 actually going to be helpful, nor to whom.  It would probably be better if
 some *packagers* showed up and asked for something that would help them
 out.  That tends not to happen, though.  Packagers are busy and often
 don't spend a lot of time proactively engaging with upstream.

 Maybe no one should use a Tahoe-LAFS packaged by anyone except the Tahoe-
 LAFS project.  That would simplify matters significantly.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1343#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage