unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Rethinking propagated inputs?
Date: Thu, 09 Sep 2021 11:48:23 +0200	[thread overview]
Message-ID: <87zgsmdqqg.fsf@gnu.org> (raw)
In-Reply-To: <7a8288c3353932507461241b96658c2224a78bf6.camel@gmail.com> (Liliana Marie Prikler's message of "Thu, 09 Sep 2021 00:55:43 +0200")

Hi Liliana,

Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:

> Am Donnerstag, den 09.09.2021, 00:12 +0200 schrieb Ludovic Courtès:

[...]

>> It would be great if the ‘Requires’ field of .pc files could specify
>> absolute file name; it would no longer be necessary to set
>> PKG_CONFIG_PATH, and thus propagation wouldn’t be needed in this
>> case.
> In that regard, would symlinking other pkg-config files as proposed
> somewhere in passing in [1] also work?  We would have to add a phase,
> that parses the Requires field from installed pkg-config files, and
> then symlinks the respective files from the inputs to gnu-build-system, 
> but since they would then exist in PKG_CONFIG_PATH and point to the
> library in question, theoretically we could get around this limitation
> of pkg-config without requiring propagation.

Why not, that could work.

>> Regarding outputs, Nixpkgs introduced a “dev” output a while back
>> that lumps together our “lib” and “include” outputs, roughly.  I
>> think that’s a good idea (for other reasons too).
> Naming-wise I'd still prefer the more concrete “lib” as “dev” to me is
> a weird umbrella term that doesn't really tell me what I'm getting
> (also it probably contributes to the distinction of users and devs, and
> as some distros like Debian have demonstrated often becomes
> pointless[2] the minute you introduce language bindings which require
> dev inputs anyway).  
>
> As far as the lib/include split in Guix is concerned, there appear to
> be few packages that split them, so “lib” effectively is “dev” in Guix
> when “out” isn't.  So apart from those outliers, is there something our
> “lib” outputs are missing that Nix' “dev” outputs include?

We’d have to check how they do it in Nix.  Basically, it’s about
reversing things: currently, everything goes to “out”, and a tiny bit
goes to “lib”.  Here, it’d be the other way around: “out” would contain
only binaries and doc (unless there’s a “doc” output), and “dev” would
contain everything else (headers, pkg-config files, cmake files, section
3 man pages, etc.)

It needs more thought and it may be hard to get right, but hopefully we
can learn from Nixpkgs here.

Now, IIRC, the Nixpkgs folks found that it didn’t have a significant
impact on closure size, contrary to what they had hoped for.  That too
needs to be taken into account.

Ludo’.


  reply	other threads:[~2021-09-09  9:48 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
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 [this message]
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=87zgsmdqqg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).