[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2502: consider switching from 'verlib' to 'packaging' for version checks

[Tahoe-LAFS]

#2502: consider switching from 'verlib' to 'packaging' for version checks
-----------------------------+---------------------------------------
     Reporter:  daira        |      Owner:  daira
         Type:  enhancement  |     Status:  assigned
     Priority:  normal       |  Milestone:  eventually
    Component:  packaging    |    Version:  1.10.1
   Resolution:               |   Keywords:  verlib packaging versions
Launchpad Bug:               |
-----------------------------+---------------------------------------

Comment (by warner):

 Or we could just delete all that code :)

 I think this this was prompted by #2499, which was prompted by my IRC-
 logged frustration when I was unable to test Tahoe against a locally-
 modified version of Foolscap, because Tahoe was being unnecessarily picky
 about versions. I spent half an hour fighting with a tool that should have
 merely said "I can't figure this out, sorry" instead of throwing
 exceptions and thwarting my efforts to get work done.

 So let me propose a guideline: all changes to the version
 displaying/checking/freaking-out-ing code in Tahoe should monotonically
 decrease in SLOC count with each commit. (er, be non-increasing.. you know
 what I mean). If 'packaging' is smaller/simpler and less-makes-it-hard-to-
 get-work-done than 'verlib', great. But I'm not really convinced that
 runtime comparison of versions is so important that it should make
 development more difficult. The next version of Foolscap is likely to
 break something in Tahoe because I was unable to test them together before
 releasing, and that's a bummer, because as far as I can tell Tahoe is the
 only user of Foolscap :).

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