unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sarah Morgensen <iskarian@mgsn.dev>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Rethinking propagated inputs?
Date: Sat, 04 Sep 2021 17:50:38 -0700	[thread overview]
Message-ID: <86h7ezkfq9.fsf@mgsn.dev> (raw)
In-Reply-To: <045891c151c74e0d66d91973c9e55e0194272df5.camel@gmail.com> (message from Liliana Marie Prikler on Sat, 04 Sep 2021 20:24:14 +0200)

Hi Liliana,

(Efraim, I've Cc'd you since you're working on re-doing Rust inputs.)

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> Does anyone have an idea how we should handle propagations for the sake
> of pkg-config?  Perhaps we could add "linked-inputs", which are added
> when building packages and environments when not using --ad-hoc, but
> not when union-building profiles.  WDYT?

I know nothing about pkg-config, but such an input would help
simplify things for Go (and I think for Rust) since many inputs need to
be propagated only at build-time.

What do you think of "build-propagated-inputs"?

(A quick search of the ML turned up one previous discussion [0]; does
anyone know of others?)

[0] https://lists.gnu.org/archive/html/guix-devel/2017-02/msg00362.html

--
Sarah


  reply	other threads:[~2021-09-05  0:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 18:24 Rethinking propagated inputs? Liliana Marie Prikler
2021-09-05  0:50 ` Sarah Morgensen [this message]
2021-09-05  7:36   ` Liliana Marie Prikler
2021-09-05  9:50     ` Bengt Richter
2021-09-05 10:50       ` Guix Jargon File (WAS: Rethinking propagated inputs?) Liliana Marie Prikler
2021-09-05 14:54         ` Bengt Richter
2021-09-05 15:28           ` Liliana Marie Prikler
2021-09-05 15:53         ` Jonathan McHugh
2021-09-06  4:07           ` Bengt Richter
2021-09-05 10:06     ` Rethinking propagated inputs? Attila Lendvai
2021-09-05 10:56       ` Julien Lepiller
2021-09-05 16:17 ` Maxime Devos
2021-09-05 16:50   ` Liliana Marie Prikler
2021-09-05 19:18     ` Maxime Devos
2021-09-05 19:37       ` Liliana Marie Prikler
2021-09-05 20:27         ` Maxime Devos
2021-09-05 21:10           ` Liliana Marie Prikler
2021-09-07 11:49             ` Maxime Devos
2021-09-07 12:22             ` 宋文武
2021-09-06 18:07     ` Maxim Cournoyer
2021-09-06 18:45       ` Liliana Marie Prikler
2021-09-07 19:01       ` Sarah Morgensen
2021-09-08  7:18         ` Liliana Marie Prikler
2021-09-08  8:24         ` iskarian
2021-09-08 22:12   ` Ludovic Courtès
2021-09-08 22:34     ` zimoun
2021-09-08 22:55     ` Liliana Marie Prikler
2021-09-09  9:48       ` Ludovic Courtès
2021-09-16 18:01         ` Hartmut Goebel
2021-09-06  7:32 ` zimoun

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=86h7ezkfq9.fsf@mgsn.dev \
    --to=iskarian@mgsn.dev \
    --cc=guix-devel@gnu.org \
    --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 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).