Bug#663017: ITP: transmission-remote-cli -- ncurses interface for the Transmission BitTorrent daemon
On 08/03/12 14:23, Leo 'costela' Antunes wrote: > On 08/03/12 13:59, Jonathan McCrohan wrote: >>> Shouldn't it be included in the transmission-cli package instead? >> >> I guess it could be included in transmission-cli. I thought >> transmission-remote-cli would be better suited to its own package >> because it a third-party transmission tool, and not part of the >> transmission project itself [1]. > > I agree it's probably better to have its own package. I also have an ITP > for transmission-remote-gtk, which is in a similar situation. > > That being said: I haven't checked the source, but I'm a bit curious > about its use of transmission-remote. Does it depend on specific > input/output formats? Did upstream at some point declare a "stable API" > for using transmission-remote in scripts? I'm just worried this might be > a small nightmare to maintain in the long run... I've been talking to upstream (t-r-cli) and the output appears to be stable between RPC versions. RPC versions don't seem to change that often in transmission, so I don't think it should be too big a deal. When it does change, support for the new RPC is added reasonably quickly. I guess an alternative would be to use transmissionrpc as a python interface to the JSON service. Jon -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f595908.1000...@gmail.com
Bug#663017: ITP: transmission-remote-cli -- ncurses interface for the Transmission BitTorrent daemon
On 08/03/12 13:59, Jonathan McCrohan wrote: >> Shouldn't it be included in the transmission-cli package instead? > > I guess it could be included in transmission-cli. I thought > transmission-remote-cli would be better suited to its own package > because it a third-party transmission tool, and not part of the > transmission project itself [1]. I agree it's probably better to have its own package. I also have an ITP for transmission-remote-gtk, which is in a similar situation. That being said: I haven't checked the source, but I'm a bit curious about its use of transmission-remote. Does it depend on specific input/output formats? Did upstream at some point declare a "stable API" for using transmission-remote in scripts? I'm just worried this might be a small nightmare to maintain in the long run... Cheers -- Leo "costela" Antunes [insert a witty retort here] -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f58c0e5.4070...@debian.org
Bug#663017: ITP: transmission-remote-cli -- ncurses interface for the Transmission BitTorrent daemon
On Jo, 08 mar 12, 12:59:19, Jonathan McCrohan wrote: > > I meant full as in full featured. Perhaps that is a bit ambiguous, I'll > reword it. Also it should be obvious from the description what benefits it brings over plain transmission-remote, especially if it ends up in a separate package. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Bug#663017: ITP: transmission-remote-cli -- ncurses interface for the Transmission BitTorrent daemon
(cc'ing Transmission maintainer Leo Costela) On 08/03/12 09:37, Andrei POPESCU wrote: > On Jo, 08 mar 12, 00:54:18, Jonathan McCrohan wrote: >> Package: wnpp >> Severity: wishlist >> Owner: Jonathan McCrohan >> >> * Package name: transmission-remote-cli >> Version : 1.1 >> Upstream Author : Ben Thompson >> * URL : https://github.com/fagga/transmission-remote-cli >> * License : GPLv3 >> Programming Lang: Python >> Description : ncurses interface for the Transmission BitTorrent daemon >> >> transmission-remote-cli is an ncurses interface for controlling the >> Transmission BitTorrent daemon. It is a full client, providing the ability to >> upload, queue and delete torrent files, monitor downloads and adjust speed >> limits. > > As far as I can tell from the above URL this is a python script (with a > .py extension), that relies on transmission-remote to do at least some > work. If this is true then you should rephrase the "It is a full client" > above. I meant full as in full featured. Perhaps that is a bit ambiguous, I'll reword it. > Shouldn't it be included in the transmission-cli package instead? I guess it could be included in transmission-cli. I thought transmission-remote-cli would be better suited to its own package because it a third-party transmission tool, and not part of the transmission project itself [1]. This would also transmission-remote-cli to be updated independently of the entire transmission package. Jon [1] It is prominently displayed on http://www.transmissionbt.com/ though. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CALouZp3tAXTSECuXPugo=rx_pzs66-qw4t8b-50g8+kmnwo...@mail.gmail.com
Bug#663017: ITP: transmission-remote-cli -- ncurses interface for the Transmission BitTorrent daemon
On Jo, 08 mar 12, 00:54:18, Jonathan McCrohan wrote: > Package: wnpp > Severity: wishlist > Owner: Jonathan McCrohan > > * Package name: transmission-remote-cli > Version : 1.1 > Upstream Author : Ben Thompson > * URL : https://github.com/fagga/transmission-remote-cli > * License : GPLv3 > Programming Lang: Python > Description : ncurses interface for the Transmission BitTorrent daemon > > transmission-remote-cli is an ncurses interface for controlling the > Transmission BitTorrent daemon. It is a full client, providing the ability to > upload, queue and delete torrent files, monitor downloads and adjust speed > limits. As far as I can tell from the above URL this is a python script (with a .py extension), that relies on transmission-remote to do at least some work. If this is true then you should rephrase the "It is a full client" above. Shouldn't it be included in the transmission-cli package instead? Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Bug#663017: ITP: transmission-remote-cli -- ncurses interface for the Transmission BitTorrent daemon
Package: wnpp Severity: wishlist Owner: Jonathan McCrohan * Package name: transmission-remote-cli Version : 1.1 Upstream Author : Ben Thompson * URL : https://github.com/fagga/transmission-remote-cli * License : GPLv3 Programming Lang: Python Description : ncurses interface for the Transmission BitTorrent daemon transmission-remote-cli is an ncurses interface for controlling the Transmission BitTorrent daemon. It is a full client, providing the ability to upload, queue and delete torrent files, monitor downloads and adjust speed limits. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120308005418.7794.27440.report...@lambda.dereenigne.org