On Wed, 2023-05-31 at 11:43 +, 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 wi
Ühel kenal päeval, K, 31.05.2023 kell 11:43, kirjutas Andrey Grozin:
> 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
> replace
On Wed, 31 May 2023, Piotr Karbowski wrote:
There's at least a few project that will not work with new wxGTK, out of what
I know that is in tree the SuperSlicer and the PrusaSlicer that in the
version currently in tree requires wxGTK 3.0. The newer version of
PrusaSlicer actually requires wxGTK
Hi,
On 31/05/2023 13.43, 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
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
