From: "Ludovic Courtès" <ludo@gnu.org>
To: iyzsong@envs.net
Cc: 65550@debbugs.gnu.org, 宋文武 <iyzsong@member.fsf.org>,
"Simon Tournier" <zimon.toutoune@gmail.com>,
"Mathieu Othacehe" <othacehe@gnu.org>,
"Tobias Geerinckx-Rice" <me@tobias.gr>,
"Josselin Poiret" <dev@jpoiret.xyz>,
"Ricardo Wurmus" <rekado@elephly.net>,
"Christopher Baines" <guix@cbaines.net>
Subject: [bug#65550] [PATCH] profiles: Don't propagate inputs for non-development packages.
Date: Sat, 09 Sep 2023 12:38:03 +0200 [thread overview]
Message-ID: <87o7ibzl6c.fsf@gnu.org> (raw)
In-Reply-To: <1f7f85189b17ebddb6d0e26afd7c5fad88c997e9.1693057951.git.iyzsong@member.fsf.org> (iyzsong@envs.net's message of "Sat, 26 Aug 2023 21:53:09 +0800")
Hello!
iyzsong@envs.net skribis:
> From: 宋文武 <iyzsong@member.fsf.org>
>
> * guix/profiles.scm (package->manifest-entry): Only include propagated inputs
> from a package for its "dev" output, or its "out" output if the package
> doesn't have a "dev" one.
What’s the rationale?
Right now, there’s only one package with an output called “dev”:
--8<---------------cut here---------------start------------->8---
$ guix package -A |cut -f3|grep dev|wc -l
1
--8<---------------cut here---------------end--------------->8---
So the focus on “dev” is debatable.
More importantly, this would break things like:
guix shell python python-scipy -C -- python3 -c 'import numpy'
… where ‘python-numpy’ is propagated by ‘python-scipy’.
Definitely not something we want to change.
WDYT?
Ludo’.
prev parent reply other threads:[~2023-09-09 10:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 11:36 Don't add propagated-inputs for all outputs 宋文武
2023-08-26 13:53 ` [bug#65550] [PATCH] profiles: Don't propagate inputs for non-development packages iyzsong--- via Guix-patches via
2023-08-26 14:21 ` Liliana Marie Prikler
2023-08-27 7:30 ` 宋文武 via Guix-patches via
2023-08-27 9:31 ` Liliana Marie Prikler
2023-08-29 10:24 ` 宋文武 via Guix-patches via
2023-08-29 17:01 ` Liliana Marie Prikler
2023-08-30 10:55 ` 宋文武 via Guix-patches via
2023-09-01 2:16 ` [bug#65550] Don't add propagated-inputs for all outputs Maxim Cournoyer
2023-08-27 7:34 ` [bug#65550] [PATCH] profiles: Don't propagate inputs for non-development packages Josselin Poiret via Guix-patches via
2023-09-01 2:34 ` [bug#65550] Don't add propagated-inputs for all outputs Maxim Cournoyer
2023-09-01 12:53 ` 宋文武 via Guix-patches via
2023-09-01 15:03 ` Maxim Cournoyer
2023-09-02 0:43 ` bug#65550: " 宋文武 via Guix-patches via
2023-09-09 10:38 ` Ludovic Courtès [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=87o7ibzl6c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=65550@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=guix@cbaines.net \
--cc=iyzsong@envs.net \
--cc=iyzsong@member.fsf.org \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@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.