all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: muradm <mail@muradm.net>, 50627@debbugs.gnu.org
Subject: [bug#50627] [PATCH 0/2] Make wayland-protocols dependency native-input.
Date: Thu, 16 Sep 2021 21:57:39 +0200	[thread overview]
Message-ID: <f6b0cca9359ae6b8e806d54f242b6fe1936c44a4.camel@gmail.com> (raw)
In-Reply-To: <20210916192331.29606-1-mail@muradm.net>

Hi,

Am Donnerstag, den 16.09.2021, 22:23 +0300 schrieb muradm:
> wayland-protocols is not runtime dependency and only build time
> dependency for applications that directly using wayland.
Guix does not distinguish between "build time" and run time
dependencies.

> Initially I tought that making wayland-protocols a native-inputs
> dependency as it should, it would reduce number of dependants on
> it. But it turns out other way around. With this patchset we are
> fixing gtk+ to not advertise it as dependency in its .pc files,
> and moving wayland-protocols to native-inputs where it should be.
That's not what native-inputs are used for.  native-inputs provide
binaries that the host/build machine needs to run in order to compile a
package.  It doesn't seem to be the case that wayland-protocols is such
a package, is it?

> Patch provided for gtk+ also merged with upstream.
> 
> Patchset prepared from core-updates-frozen. While it seems that
> it will impact many other packages, actually this patch reduces
> number of packages that touches wayland-protocols and probably
> avoids it at runtime.
But it still impacts a large number of packages in ways that could
potentially break and haven't been tested, right?  While reducing
closure size is generally a good thing, I think we do need to be
careful whenever "build time vs. run time" and native vs. non-native
are confused.

Regards





  parent reply	other threads:[~2021-09-16 19:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 19:23 [bug#50627] [PATCH 0/2] Make wayland-protocols dependency native-input muradm
2021-09-16 19:26 ` [bug#50627] [PATCH 1/2] gnu: gtk: Move wayland-protocols to native-inputs muradm
2021-09-16 19:26   ` [bug#50627] [PATCH 2/2] gnu: Fix wayland-protocols dependency to be in native-inputs muradm
2021-09-16 19:57 ` Liliana Marie Prikler [this message]
2021-09-17  2:35   ` [bug#50627] [PATCH 0/2] Make wayland-protocols dependency native-input muradm
2021-09-17  7:46     ` Liliana Marie Prikler
2021-09-17  8:20       ` muradm
2021-09-17 13:01         ` Liliana Marie Prikler
2021-09-17 14:11           ` muradm
2021-09-17 17:01             ` Liliana Marie Prikler
2021-09-17 14:11 ` [bug#50627] [PATCH v1] gnu: gtk: Move wayland-protocols to inputs muradm
2022-10-06  8:18 ` Maxime Devos via Guix-patches

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f6b0cca9359ae6b8e806d54f242b6fe1936c44a4.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=50627@debbugs.gnu.org \
    --cc=mail@muradm.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.