public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: Mart Raudsepp <leio@gentoo.org>, gentoo-dev@lists.gentoo.org
Cc: gnome@gentoo.org, xfce@gentoo.org, binhost@gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/5] gui-libs/gtk: add a "poison" macro support to disable X/wayland
Date: Wed, 3 Jul 2024 13:26:09 -0400	[thread overview]
Message-ID: <0561fd4c-3efa-49e0-84d1-b71c32504627@gmail.com> (raw)
In-Reply-To: <b2b6469873df58c0025f2782a6eed7da284fb638.camel@gentoo.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1085 bytes --]

On 7/3/24 7:16 AM, Mart Raudsepp wrote:
> Please do see about approaching upstream about this in the context of
> GTK4 in a constructive friendly manner, perhaps from the angle of how
> to transition any distribution to a GTK that does not include X11
> support with less migrational pain - this should be of interest for
> more cases than Gentoo.
> 
> Maybe the idea about selecting backend stubs to include for their API
> functions, which would just end up returning what a fully enabled
> backend would return when the running environment is NOT that backend
> (e.g. when gdk-x11 functions are called in a wayland native app or gdk-
> wayland functions are called when X11 or Xwayland is in use).
> 
> If that gains some traction, maybe we could also do this for GTK3 as
> well.
> 
> Given how we'd have to end up maintaining this long term, such upstream
> discussions are sort of a soft blocker for proceeding with the
> patchset, as far as I'm concerned.


Filed as https://gitlab.gnome.org/GNOME/gtk/-/issues/6832, fingers crossed.


-- 
Eli Schwartz

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

  reply	other threads:[~2024-07-03 17:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23 17:35 [gentoo-dev] [PATCH 0/5] Fixing automagic dependencies on gtk[wayland,X], Eli Schwartz
2024-06-23 17:35 ` [gentoo-dev] [PATCH 1/5] gui-libs/gtk: add a "poison" macro support to disable X/wayland Eli Schwartz
2024-06-24  9:08   ` Florian Schmaus
2024-06-26  9:03   ` Sam James
2024-06-27  4:52     ` Eli Schwartz
2024-06-27  4:58       ` Sam James
2024-07-03 11:16         ` Mart Raudsepp
2024-07-03 17:26           ` Eli Schwartz [this message]
2024-06-23 17:35 ` [gentoo-dev] [PATCH 2/5] net-libs/gtk-vnc: prevent automagically building against gtk[X,wayland] Eli Schwartz
2024-06-23 17:35 ` [gentoo-dev] [PATCH 3/5] x11-libs/wxGTK: " Eli Schwartz
2024-06-23 17:35 ` [gentoo-dev] [PATCH 4/5] xfce-base/libxfce4ui: prevent automagically building against gtk[wayland] Eli Schwartz
2024-06-23 17:35 ` [gentoo-dev] [PATCH 5/5] dev-libs/libportal: prevent automagically building against gtk[X,wayland] Eli Schwartz
2024-06-23 18:33 ` [gentoo-dev] [PATCH 0/5] Fixing automagic dependencies on gtk[wayland,X], James Le Cuirot
2024-06-26  9:02 ` Sam James

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=0561fd4c-3efa-49e0-84d1-b71c32504627@gmail.com \
    --to=eschwartz93@gmail.com \
    --cc=binhost@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gnome@gentoo.org \
    --cc=leio@gentoo.org \
    --cc=xfce@gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox