> Interesting, does this mean the existing "gui" output of transmission
> installs transmission-qt.desktop even though it doesn't include
> transmission-qt? If so, that seems like a bug to me.
>
No, no, the default transmission package doesn't create a
transmission-qt.desktop file. I was just referring to my own package,
which creates builds and creates the desktop file for both
transmission-qt and transmission-gtk (since it has the required
dependencies for both), and then moves the transmission-gtk binary and
the desktop files into the the :gui output due to the inherited
'move-gui phase.
It moves the transmission-qt.desktop file as well because part of the
'move-gui phase is this:
(for-each
(lambda (dir)
(rename-file (string-append #$output "/share/" dir)
(string-append #$output:gui "/share/" dir)))
'("applications" "icons" "metainfo"))
> I *personally* lean towards separate packages, because I think
> packages are easier to find than outputs; and because it reduces the
> build footprint, due to needing fewer inputs. Right now, if you build
> transmission, it needs the gtk libraries, even if you don't build the
> gui output. So I think the best thing here is three packages:
> transmission (daemon only), transmission-gtk, and transmission-qt --
> where the latter two are derived from the former.
Yeah, I would prefer that as well. And adding Qt as an additional
dependency makes that situation worse.
