[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Specify runtime dependencies with propagated-inputs or wrapper scripts

From: Léo Le Bouter
Subject: Specify runtime dependencies with propagated-inputs or wrapper scripts
Date: Fri, 26 Mar 2021 20:36:38 +0100
User-agent: Evolution 3.34.2


I often meet problems where some packages don't work out of the box
because they have some runtime dependencies like themes or third party

I solved these problems on occasion by making commits such as this:
- which adds a wrapper script to "bin/chromium" and includes xdg-utils
in PATH variable.

It works but it's tedious to do for each and every binary in every
single package.

I see we also have a propagated-inputs field, which looks nice but for
some reason people advice against using it. For what reasons? It is not
as tedious as wrappers and I would really like to be able to specify
runtime dependencies of packages using it without problems.

I think we must find a solution to this runtime dependencies problem
that is better than wrapper scripts because they are very tedious to
create for every single binary in every single package.

Another recent example being that the caja package depends on dconf to
change it's settings, which is not installed by default when users use
window managers like sway.

Let's find a convenient solution here that would allow us to put an end
to these problems that affect many new users and remains obscure for
them that they would need to add additional packages in their
configuration (and which).


Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]