From: jlicht@fsfe.org
To: 64155@debbugs.gnu.org
Cc: Jelle Licht <jlicht@fsfe.org>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
Andrew Tropin <andrew@trop.in>, Andrew Tropin <andrew@trop.in>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#64155] [PATCH v2 1/2] gnu: emacs-piem: Do not propagate any inputs.
Date: Mon, 19 Jun 2023 21:35:53 +0200 [thread overview]
Message-ID: <374d72df7d5150bcd55de15d6b299531c5ec86c6.1687203327.git.jlicht@fsfe.org> (raw)
In-Reply-To: <97c1eb6e58e07feaef29a1b10eeabb09f870bee1.1687117071.git.jlicht@fsfe.org>
From: Jelle Licht <jlicht@fsfe.org>
* gnu/packages/emacs-xyz.scm (emacs-piem) [propagated-inputs]: Remove, moving
emacs-elfeed and emacs-notmuch to...
[inputs]: ...here.
---
(no changes since v1)
gnu/packages/emacs-xyz.scm | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index f46af73aec..416656f243 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -8357,9 +8357,8 @@ (define-public emacs-piem
("piem-b4-b4-executable"
(search-input-file inputs "/bin/b4"))))))))
(inputs
- (list b4))
- (propagated-inputs
- (list emacs-elfeed
+ (list b4
+ emacs-elfeed
emacs-notmuch))
(home-page "https://docs.kyleam.com/piem")
(synopsis "Glue for working with public-inbox archives")
base-commit: d884fc9e2efecfba09af4694f5a13ad7fc6f704f
--
2.40.1
next prev parent reply other threads:[~2023-06-19 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 19:38 [bug#64155] [PATCH] gnu: emacs-piem: Update to 0.5.0 jlicht
2023-06-19 13:44 ` Andrew Tropin
2023-06-19 15:39 ` Jelle Licht
2023-06-19 16:32 ` Andrew Tropin
2023-06-19 18:24 ` Liliana Marie Prikler
2023-06-19 19:35 ` jlicht [this message]
2023-06-19 19:35 ` [bug#64155] [PATCH v2 2/2] " jlicht
2023-06-20 3:23 ` Andrew Tropin
2023-06-20 19:10 ` bug#64155: " Jelle Licht
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=374d72df7d5150bcd55de15d6b299531c5ec86c6.1687203327.git.jlicht@fsfe.org \
--to=jlicht@fsfe.org \
--cc=64155@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=liliana.prikler@gmail.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 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.