unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: jgart <jgart@dismail.de>
Cc: 59372@debbugs.gnu.org, paren@disroot.org
Subject: [bug#59372] [PATCH] gnu: peek: Add missing input.
Date: Mon, 21 Nov 2022 21:18:32 +0100	[thread overview]
Message-ID: <8735acjbu4.fsf@nckx> (raw)
In-Reply-To: <20221121082715.GE10046@dismail.de>

[-- Attachment #1: Type: text/plain, Size: 391 bytes --]

jgart 写道：
> peek, needs either ffmpeg or gnome shell to be present.
> How should I handle that in Guix?

Ideally: let peek pop up the window asking the user to install 
ffmpeg.

Then the user installs ffmpeg only if it's actually needed, and 
isn't ‘forced’ to pay the cost if it's not.

Does it not show that window on a foreign distribution?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2022-11-21 20:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  1:27 [bug#59372] [PATCH] gnu: peek: Add missing input jgart via Guix-patches via
2022-11-19  2:50 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-19  4:07   ` jgart via Guix-patches via
2022-11-19  9:38     ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 14:27       ` jgart via Guix-patches via
2022-11-21 15:14         ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 20:18         ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-11-21 20:58           ` jgart via Guix-patches via
2023-01-29  6:02             ` bug#59372: " 宋文武 via Guix-patches via
2022-11-21 17:13   ` [bug#59372] " zimoun
2022-11-21 19:38     ` jgart via Guix-patches via
2022-11-22 14:39       ` zimoun
2022-11-22 18:29         ` jgart via Guix-patches via
2022-11-19  9:13 ` ( via Guix-patches via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8735acjbu4.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=59372@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=me@tobias.gr \
    --cc=paren@disroot.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).