From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>, guix-devel@gnu.org
Subject: Re: Rethinking propagated inputs?
Date: Tue, 07 Sep 2021 13:49:56 +0200 [thread overview]
Message-ID: <edb84bf91d6eb76abcaf180fbb2dddf59e4de282.camel@telenet.be> (raw)
In-Reply-To: <7522a0488c02f459a02bf0aa9e6a36d9d8f31d0b.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3220 bytes --]
Liliana Marie Prikler schreef op zo 05-09-2021 om 23:10 [+0200]:
> Am Sonntag, den 05.09.2021, 22:27 +0200 schrieb Maxime Devos:
> > Liliana Marie Prikler schreef op zo 05-09-2021 om 21:37 [+0200]:
> > > > > 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.
> > >
> > > Is that so? I would think the build process needs to see stuff
> > > outside of its inputs for that to work, e.g. the actual header it
> > > wants to include, which isn't part of "build". Am I
> > > misunderstanding our sandbox requirements?
> >
> > The .pc file includes the absolute path to the library and include
> > directories, so the output "build" with the .pc file has a reference
> > to the output "out" with the libraries and include headers. More
> > concretely, take the .pc from the glib package:
> >
> > prefix=/gnu/store/98hgv3i6hdqgiq98ldy7rkpdwhah8iq2-glib-2.62.6
> > libdir=${prefix}/lib
> > includedir=${prefix}/include
> > [more stuff]
> > Requires.private: libpcre >= 8.31
> > Libs: -L${libdir} -lglib-2.0
> > Libs.private: -pthread
> > Cflags: -I${includedir}/glib-2.0 -I${libdir}/glib-2.0/include
> >
> > The (transitive) references of all inputs to the build process are
> > included in the sandbox. In this case, if the package has the
> > hypothetical glib:build among its inputs, the daemon will
> > automatically make glib:out available as well in the sandbox.
> And IIUC if glib had a "lib" output, glib:lib would be available in the
> sandbox instead of glib:out due to the reference by glib:build?
If a package has the proposed 'glib:build' in its (propagated-)inputs,
and if 'glib' had a 'lib' output, then in the build sandbox of the package,
'glib:lib' will be available.
> If
> that's the case using #:by and "build" outputs might be a preferable
> solution, if not for all packages then at least for some.
> At this point the question then becomes what to name this "build"
> output and what to put into it besides pkg-config stuff. Particularly
> in the land of glib, there also exist typelibs, which can be used as
> "build" inputs in the case of Vala or as runtime inputs in the case of
> pygobject and other language bindings. Perhaps this is early
> bikeshedding when we'd actually need to code up #:by, but what would be
> the better approach here? Separate "build" into "pkg-config", "cmake"
> (for CMake-based package discovery), "typelib" etc. or have one more or
> less anonymous blob called "build"?
I don't know (-:. Maybe let's just start with pkg-config and #:by?
for now? The name can always be changed later.
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-07 11:51 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 [this message]
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=edb84bf91d6eb76abcaf180fbb2dddf59e4de282.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).