From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Rethinking propagated inputs?
Date: Mon, 06 Sep 2021 14:07:21 -0400 [thread overview]
Message-ID: <87lf49a886.fsf@gmail.com> (raw)
In-Reply-To: <5ba200792813bb0967e388911320b741cf98d90d.camel@gmail.com> (Liliana Marie Prikler's message of "Sun, 05 Sep 2021 18:50:14 +0200")
Hello,
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Hi
>
> Am Sonntag, den 05.09.2021, 18:17 +0200 schrieb Maxime Devos:
>> Liliana Marie Prikler schreef op za 04-09-2021 om 20:24 [+0200]:
>> > Hi Guix,
>> >
>> > some while ago we made the decision to propagate inputs, that are
>> > mentioned in pkg-config files, the rationale being that those
>> > propagated inputs will be needed in packages in order to
>> > compile. This
>> > has saved us some typing, but at a cost. For instance, it is now
>> > no
>> > longer possible to upgrade "zile"
>>
>> Zile doesn't propagate glib: it's in inputs, not propagated-inputs:
>> https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/zile.scm#n84.
> Oops, what a blunder. It turns out my mistake was
>> > " and "icecat" independently, because
>> > both propagate glib. "libreoffice" and "telegram-desktop", two
>> > packages that have failed us loudly before, are also in that list.
>>
>> libreoffice doesn't propagate anything. Neither does icecat.
It seems the original issue pointed at was somewhat misguided; is there
still something to be fixed about propagated inputs? It seems the
discussion has moved toward handling propagated inputs for the use of
pkg-config.
What are the current problems with it, and what would the advantages be
to move away from the status quo? If there aren't clear benefits, I'd
prefer the status quo, abstaining from the added complexity.
Thanks,
Maxim
next prev parent reply other threads:[~2021-09-06 18:07 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
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 [this message]
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=87lf49a886.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--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).