From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] wxGTK:3.0-gtk3 vs wxGTK:3.2-gtk3
Date: Wed, 31 May 2023 20:44:20 +0100 [thread overview]
Message-ID: <0ab2b58bc799d4c0de7634b91c7dca1b9cc67ea0.camel@gentoo.org> (raw)
In-Reply-To: <cbfdb37a-bb7-103c-ca4b-d1c08d87ad19@woodpecker.gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On Wed, 2023-05-31 at 11:43 +0000, Andrey Grozin wrote:
> Hello *,
>
> wxGTK:3.2-gtk3 is now stable. But there are 98 ebuilds depending on
> wxGTK:3.0-gtk3 and only 22 ebuilds depending on wxGTK:3.2-gtk3 in the
> tree. Probably, in a vast majority of cases 3.0 can be simply replaced by
> 3.2 without any negative consequences. What could be a reasonable way to
> organize the transition 3.0 -> 3.2 in the tree? File a zillion bugs?
>
> The fact that this dependence is written in a special syntax
> WX_GTK_VER="3.0-gtk3"
> makes such a transition more difficult. Unlike the normal dependency
> syntax, it is not possible to write something like
> x11-libs/wxGTK:*=
> This is unfortunate. The 3.0 -> 3.2 transition absolutely requires to edit
> ebuild texts, unlike :*= where the same ebuild can work with different
> slots (just a recompilation is sufficient for transition). This fact
> makes it impossible for an ebuild to work with both slots. In a majority
> of cases, I suppose, it would be desirable to allow an ebuild to work with
> any of these 2 slots, without a necessity to edit it. But, alas, this is
> not possible.
>
> Andrey
games-engines/odamex is another one that doesn't work with 3.2. It just
crashes. Haven't looked into it.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
prev parent reply other threads:[~2023-05-31 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 11:43 [gentoo-dev] wxGTK:3.0-gtk3 vs wxGTK:3.2-gtk3 Andrey Grozin
2023-05-31 11:55 ` Piotr Karbowski
2023-05-31 12:03 ` Andrey Grozin
2023-05-31 12:53 ` Mart Raudsepp
2023-05-31 19:44 ` James Le Cuirot [this message]
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=0ab2b58bc799d4c0de7634b91c7dca1b9cc67ea0.camel@gentoo.org \
--to=chewi@gentoo.org \
--cc=gentoo-dev@lists.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