From: zimoun <zimon.toutoune@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 26170@debbugs.gnu.org
Subject: bug#26170: Bug #26170 Hunting: doc: Explanation of propagated-inputs unclear
Date: Wed, 09 Sep 2020 15:25:31 +0200 [thread overview]
Message-ID: <87h7s7ulo4.fsf@gmail.com> (raw)
In-Reply-To: <20191203124904.lotocvk7htki2ill@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Tue, 3 Dec 2019 13:49:04 +0100")
Dear,
The bug 26170 [1] is about the description of “propagated inputs” in the
manual.
Currently, the term “propagated inputs” in the index [2] goes to the
section “Invoking guix package” [3] and explaining:
Sometimes packages have propagated inputs: these are
dependencies that automatically get installed along with the
required package (see propagated-inputs in package objects, for
information about propagated inputs in package definitions).
An example is the GNU MPC library: its C header files refer to
those of the GNU MPFR library, which in turn refer to those of
the GMP library. Thus, when installing MPC, the MPFR and GMP
libraries also get installed in the profile; removing MPC also
removes MPFR and GMP—unless they had also been explicitly
installed by the user.
with the hyperlink [4] mentioning:
Lastly, propagated-inputs is similar to inputs, but the
specified packages will be automatically installed alongside the
package they belong to (see guix package, for information on how
guix package deals with propagated inputs).
For example this is necessary when a C/C++ library needs headers
of another library to compile, or when a pkg-config file refers
to another one via its Requires field.
Another example where propagated-inputs is useful is for
languages that lack a facility to record the run-time search
path akin to the RUNPATH of ELF files; this includes Guile,
Python, Perl, and more. To ensure that libraries written in
those languages can find library code they depend on at run
time, run-time dependencies must be listed in propagated-inputs
rather than inputs.
The initial suggestions of this bug report were:
--8<---------------cut here---------------start------------->8---
1) that `propagated-inputs` are automatically installed *to the Guix
profile* and not just the Store like regular inputs and
2) that C/C++ libraries do not need to be propagated because they can
just as well be loaded from the Store *unless* their header files are
included by header files of another input package (?) and
3) more examples like the above example for GNOME Evolution (which
however I have yet to finish packaging and submit as a patch; maybe
dconf is a better example – I presume it is also needed at run time and
not just).
--8<---------------cut here---------------end--------------->8---
which now appear to me clarified with the current manual.
Does it make sense to close?
All the best,
simon
[1] http://issues.guix.gnu.org/issue/26170 [2]
http://guix.gnu.org/manual/devel/en/guix.html#Concept-Index_cp_letter-P
[3]
http://guix.gnu.org/manual/devel/en/guix.html#index-propagated-inputs
[4] http://guix.gnu.org/manual/devel/en/guix.html#package_002dpropagated_002dinputs
next prev parent reply other threads:[~2020-09-09 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 7:03 bug#26170: documentation: Explanation of propagated-inputs unclear pelzflorian (Florian Pelz)
2019-12-03 12:14 ` bug#26170: Bug #26170 Hunting: doc: " zimoun
2019-12-03 12:49 ` pelzflorian (Florian Pelz)
2020-09-09 13:25 ` zimoun [this message]
2020-09-09 15:10 ` pelzflorian (Florian Pelz)
2020-09-09 15:45 ` zimoun
2020-09-16 10:37 ` Ludovic Courtès
2020-09-16 13:27 ` pelzflorian (Florian Pelz)
2020-09-17 19:45 ` Ludovic Courtès
2020-09-18 9:08 ` pelzflorian (Florian Pelz)
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=87h7s7ulo4.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=26170@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).