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
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
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.
K
(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
>> Upstrea
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
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
6 matches
Mail list logo
