From: Bodertz <bodertz@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Add transmission-qt to the transmission package?
Date: Sat, 21 Dec 2024 15:27:04 -0700 [thread overview]
Message-ID: <87seqgu0xz.fsf@gmail.com> (raw)
In-Reply-To: 952935df-fca8-4ee8-859c-2c49ff33236e@app.fastmail.com
> 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.
prev parent reply other threads:[~2024-12-21 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 17:39 Add transmission-qt to the transmission package? Bodertz
2024-12-21 19:38 ` Ian Eure
2024-12-21 22:27 ` Bodertz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87seqgu0xz.fsf@gmail.com \
--to=bodertz@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.