unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Zhu Zihao <all_but_last@163.com>, 49219@debbugs.gnu.org
Subject: [bug#49219] Acknowledgement ([PATCH]: Update emacs-telega.)
Date: Fri, 25 Jun 2021 08:23:54 +0200	[thread overview]
Message-ID: <cf2e2b5e35b257d806b7eb3fe0816620eea036b2.camel@student.tugraz.at> (raw)
In-Reply-To: <86h7hm8oth.fsf@163.com>

Am Freitag, den 25.06.2021, 14:02 +0800 schrieb Zhu Zihao:
> Update patches:
W.r.t. the propagation of ffmpeg and libwebp I don't think we'd want to
force either onto the user (particularly ffmpeg might collide with a
different version they've already installed).  If finding and replacing
all instances of "ffmpeg" with its full path is too broad, perhaps you
could add procedures that find it or replace instances of ffmpeg as a
binary with @ffmpeg@.  I think a variable or procedure called telega-
ffmpeg-command might even be acceptable by upstream and broader Emacs
standards.
If on the other hand you want the user's versions of those packages to
be the one that's used, simply don't propagate it.

Regards,
Leo





  reply	other threads:[~2021-06-25  6:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25  5:48 [bug#49219] [PATCH]: Update emacs-telega Zhu Zihao
     [not found] ` <handler.49219.B.162460012825885.ack@debbugs.gnu.org>
2021-06-25  6:02   ` [bug#49219] Acknowledgement ([PATCH]: Update emacs-telega.) Zhu Zihao
2021-06-25  6:23     ` Leo Prikler [this message]
2021-06-25  9:31       ` Zhu Zihao
2021-06-25 10:46         ` Leo Prikler
2021-06-26 13:16       ` Zhu Zihao
2021-06-28  2:53         ` Zhu Zihao
2021-07-06  3:04           ` Zhu Zihao
2021-07-07 13:51         ` Giovanni Biscuolo
2021-07-09 10:36           ` Zhu Zihao
2021-07-09 11:27             ` Leo Prikler
2021-07-09 13:15               ` bug#49219: " Leo Prikler

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=cf2e2b5e35b257d806b7eb3fe0816620eea036b2.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=49219@debbugs.gnu.org \
    --cc=all_but_last@163.com \
    /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).