From: Nicolas Goaziou via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
67537-done@debbugs.gnu.org, Sergey Trofimov <sarg@sarg.org.ru>,
Andrew Tropin <andrew@trop.in>
Subject: bug#67537: [PATCH 0/4] Update weirdware packages.
Date: Thu, 04 Jan 2024 12:38:43 +0100 [thread overview]
Message-ID: <87edexjpks.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <bd813759e0d388e39b585020d3c2b82ae047c548.camel@gmail.com> (Liliana Marie Prikler's message of "Wed, 29 Nov 2023 22:55:22 +0100")
Hello,
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Am Mittwoch, dem 29.11.2023 um 22:31 +0100 schrieb Sergey Trofimov:
>> Hello guix,
>>
>> I've noticed that recently added weirdware emacs packages use
>> `inputs` to
>> declare dependencies. I think `propagated-inputs` make more sense
>> here as
>> these are required in runtime.
>>
>> Sergey Trofimov (4):
>> gnu: emacs-dnt: Propagate inputs.
>> gnu: emacs-debase: Remove unused inputs.
>> gnu: emacs-discomfort: Propagate inputs.
>> gnu: emacs-hyperspace: Propagated inputs.
> Nice catch. LGTM.
Applied. Thanks.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2024-01-04 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 21:31 [bug#67537] [PATCH 0/4] Update weirdware packages Sergey Trofimov
2023-11-29 21:33 ` [bug#67537] [PATCH 1/4] gnu: emacs-dnt: Propagate inputs Sergey Trofimov
2023-11-29 21:33 ` [bug#67537] [PATCH 2/4] gnu: emacs-debase: Remove unused inputs Sergey Trofimov
2023-11-29 21:33 ` [bug#67537] [PATCH 3/4] gnu: emacs-discomfort: Propagate inputs Sergey Trofimov
2023-11-29 21:33 ` [bug#67537] [PATCH 4/4] gnu: emacs-hyperspace: Propagated inputs Sergey Trofimov
2023-11-29 21:55 ` [bug#67537] [PATCH 0/4] Update weirdware packages Liliana Marie Prikler
2024-01-04 11:38 ` Nicolas Goaziou via Guix-patches via [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=87edexjpks.fsf@nicolasgoaziou.fr \
--to=guix-patches@gnu.org \
--cc=67537-done@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=liliana.prikler@gmail.com \
--cc=mail@nicolasgoaziou.fr \
--cc=sarg@sarg.org.ru \
/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.