Re: Rethinking propagated inputs?

[Maxim Cournoyer]

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