On Mon, Jan 28, 2013 at 08:21:09PM +0100, Cristian Greco wrote: > First of all, I apologize for not taking care of the huge amount of > bugs with deluge lately. > > I tend to disagree with the proposed patch. The current situation of > deluge dependencies is *exactly* as it was intended: the reason is > clearly (IMHO) stated in packages description; and it is the result > of a discussion which also involved upstream authors and led to the > kind of fragmentation of dependencies we all see. > > The patch proposed to fix this bug is a complete revert of the change at > [0], which in turn was discussed and agreed with upstream in order to > fix the bug at [1] and to make it clear the client-server model of > deluge and the role of its UIs packages. > > Having said that, I'd prefer to leave package' dependencies untouched, > and instead ask you for suggestions on how to improve their descriptions > and make it clear to the final user why and when she or he should > choose to install `deluge` rather than `deluge-gtk` (maybe the name of > the package is also unfortunate here and helps causing confusion). > > [0] > http://anonscm.debian.org/gitweb/?p=collab-maint/deluge.git;a=commitdiff;h=c9647e5e55e3fa89b4b4073708b291c3c08a23f9 > [1] https://bugs.launchpad.net/ubuntu/+source/deluge/+bug/672069 There is only one change needed: if an user installs just deluge-gtk they shouldn't get the classic mode enabled by default. I'm not sure that this is possible at all, though.
-- WBR, wRAR
signature.asc
Description: Digital signature
