From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, guix-devel@gnu.org
Subject: Re: Rethinking propagated inputs?
Date: Sun, 05 Sep 2021 21:18:00 +0200 [thread overview]
Message-ID: <4de577e44d3d7e4099266646f0f20686bb111f08.camel@telenet.be> (raw)
In-Reply-To: <5ba200792813bb0967e388911320b741cf98d90d.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3065 bytes --]
Liliana Marie Prikler schreef op zo 05-09-2021 om 18:50 [+0200]:
>
[...]
> > (Feel free to suggest a more concise name.)
> Since "propagated" is already given by propagated-inputs, what about
> simply having #:by?
> E.g. something like: [...]
> (define glib
> (package
> (name "glib")
> (outputs '("out" ; everything
> "bin")) ; glib-mkenums ... depends on Python
> (propagated-inputs
> `(("pcre" ,pcre #:by ("out")) ; future-proof #:by
> ("libffi" ,libffi #:by ("out")) ; have it be a list
> [...]))
That looks nice, thanks.
> I'm not sure whether we need to necessarily add a new "build" output
> for pkg-config, that'd lead to a lot of doubly-propagated includes.
> (Imagine both libffi and libffi:build etc.) I think the more
> meaningful division here would be to add "bin" or "lib" outputs to
> those packages, where we don't want propagation to continue
> indefinitely.
Putting pkg-config files into the "lib" or "out" output (together with shared libraries)
seems reasonable to me ("lib" if the package is usually used as a binary,
but also has libaries with pkg-config files, and "out" if it is usually
used as a library).
> This does cause problems with language bindings though,
> e.g. pygobject, as those also propagate the package in question and
> can't be neatly separated.
python-pygobject can just keep everything in the output "out",
and let glib and libffi be propagated by "out", no? I don't see
how this would cause trouble for language bindings.
> > Now, imagine the "build" output of "zile" had glib:build in
> > propagated-inputs, using the scheme described above. Then, if the
> > "out" output of zile is installed in a profile, that doesn't cause
> > glib to appear in the profile as well, because glib
> > is only propagated for the "build" output of zile, and not for "out"
> > output of zile.
> >
> > However, if "build" is installed in the profile (e.g. because someone
> > runs "guix environment --ad-hoc zile:build various compilation tools"
> > to create an application using the zile library), then the .pc
> > becomes available in the profile.
> I must admit that this solution appears to have some surface elegance,
> but what exactly would go in the "build" output of a package? You
> mentioned pkg-config files (obviously), but those don't suffice to
> actually build a package, do they?
Sometimes they do suffice. The .pc files contain the "-L/.../LIB",
"-I/.../include" and "-lstuff" flags needed for compilation. If the
build system of the package uses pkg-config, it will use those flags,
so the compiler will find the library in that case.
Not sure if they always do suffice.
> Would we need an extra syntax to
> e.g. propagate the "out" output by "build" (and in some cases the "lib"
> output instead)?
Not if .pc files are put in "out" (or "lib" in some cases) instead of the
originally proposed "build", but otherwise, possibly?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-09-05 19:19 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 [this message]
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=4de577e44d3d7e4099266646f0f20686bb111f08.camel@telenet.be \
--to=maximedevos@telenet.be \
--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).