Changes between Initial Version and Version 1 of Ticket #43975
- Timestamp:
- Jun 10, 2014, 1:20:09 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #43975
- Property Owner changed from macports-tickets@… to perry@…
- Property Port cfv added
-
Ticket #43975 – Description
initial v1 1 1 The port cfv prominently lists the ability to create and test torrent files amongst its features, however this functionality is dependent upon some Python module providing the ability to read the files: 2 2 3 {{{ 3 4 tjcarter@amaya:~/test$ cfv -t torrent -f test.torrent 4 5 test.torrent : No module named BTL and No module named BitTorrent and No module named BitTornado (CF) 5 6 0 files, 0 OK, 1 chksum file errors. 0.000 seconds, 0.0K/s 7 }}} 6 8 7 9 The only module that satisfies this requirement in MacPorts is the one included with bittornado. Which appears to be inexplicably hardcoded to use python25 for some reason of portfile-fu I do not comprehend—not that I can ever claim to have actually ever understood ANY portfile, mind you… So far as I understand, I should be able to satisfy this undeclared dependency by changing the line reading 8 10 11 {{{ 9 12 python.default_version 25 13 }}} 10 14 11 15 to 12 16 17 {{{ 13 18 python.default_version 27 19 }}} 14 20 15 21 and installing bittornado. And if that worked, I'd have a ticket against bittornado with the trivial portfile patch. :) But it didn't, and I couldn't begin to know how to fix it. So instead I do the only thing I can do: I note the problem I was originally trying to solve (that cfv doesn't actually have any means of supporting torrent files as is indicated) and giving you the option to decide how to resolve it.