[MacPorts] #43975: cfv 1.18.3 doesn't support .torrent files

[MacPorts]

#43975: cfv 1.18.3 doesn't support .torrent files
-------------------------+---------------------
  Reporter:  tjcarter@…  |      Owner:  perry@…
      Type:  defect      |     Status:  new
  Priority:  Low         |  Milestone:
 Component:  ports       |    Version:  2.3.0
Resolution:              |   Keywords:
      Port:  cfv         |
-------------------------+---------------------
Changes (by ryandesign@…):

 * owner:  macports-tickets@… => perry@…
 * port:   => cfv


Old description:

> 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:
>
> tjcarter at amaya:~/test$ cfv -t torrent -f test.torrent
> test.torrent : No module named BTL and No module named BitTorrent and No
> module named BitTornado (CF)
> 0 files, 0 OK, 1 chksum file errors.  0.000 seconds, 0.0K/s
>
> 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
>
> python.default_version 25
>
> to
>
> python.default_version 27
>
> 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.
>
> I do consider removing the claim of torrent support a resolution—the idea
> of making one of the requisite modules available in either python27 or
> python32 exists, but as I'm not willing to bash my head against it
> anymore, I certainly don't expect anyone else to.  ;)

New description:

 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:

 {{{
 tjcarter at amaya:~/test$ cfv -t torrent -f test.torrent
 test.torrent : No module named BTL and No module named BitTorrent and No
 module named BitTornado (CF)
 0 files, 0 OK, 1 chksum file errors.  0.000 seconds, 0.0K/s
 }}}

 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

 {{{
 python.default_version 25
 }}}

 to

 {{{
 python.default_version 27
 }}}

 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.

 I do consider removing the claim of torrent support a resolution—the idea
 of making one of the requisite modules available in either python27 or
 python32 exists, but as I'm not willing to bash my head against it
 anymore, I certainly don't expect anyone else to.  ;)

--

-- 
Ticket URL: <https://trac.macports.org/ticket/43975#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X