Re: remove x11/wxglade

2023-10-17 Thread Theo Buehler
On Tue, Oct 17, 2023 at 04:05:17PM +0200, Antoine Jacoutot wrote:
> On Sun, Oct 15, 2023 at 11:26:44AM -0400, Thomas Frohwein wrote:
> > On Sun, Oct 15, 2023 at 11:18:16AM -0400, Thomas Frohwein wrote:
> > 
> > [...]
> > 
> > > +USE_NOBTCFI= Yes
> > > +USE_WXALLOWED=   Yes
> > 
> > Ignore these, it was just me blindly trying something which shouldn't
> > make its way into any potential update of the port.
> 
> OK to remove this port, anyone?

ok tb



Re: remove x11/wxglade

2023-10-17 Thread Antoine Jacoutot
On Sun, Oct 15, 2023 at 11:26:44AM -0400, Thomas Frohwein wrote:
> On Sun, Oct 15, 2023 at 11:18:16AM -0400, Thomas Frohwein wrote:
> 
> [...]
> 
> > +USE_NOBTCFI=   Yes
> > +USE_WXALLOWED= Yes
> 
> Ignore these, it was just me blindly trying something which shouldn't
> make its way into any potential update of the port.

OK to remove this port, anyone?

-- 
Antoine



Re: remove x11/wxglade

2023-10-15 Thread Stefan Hagen
Thomas Frohwein wrote (2023-10-15 18:34 CEST):
> On Sun, Oct 15, 2023 at 06:01:57PM +0200, Stefan Hagen wrote:
> > Thomas Frohwein wrote (2023-10-15 17:26 CEST):
> > > On Sun, Oct 15, 2023 at 11:18:16AM -0400, Thomas Frohwein wrote:
> > > 
> > > [...]
> > > 
> > > > +USE_NOBTCFI=   Yes
> > > > +USE_WXALLOWED= Yes
> > > 
> > > Ignore these, it was just me blindly trying something which shouldn't
> > > make its way into any potential update of the port.
> > 
> > I authenticated, and downloaded Blazing Sails and Q.U.B.E 2.
> > Works almost as advertised.
> > 
> > Almost, because the games got installed to ~/Games/QUBE2 and 
> > ~/Games/BlazingSails.
> > 
> > Portwise, maybe one or two more newlines at appropriate places before 
> > committing?
> > 
> > OK for import sdk@
> 
> I assume the ok is for legendary, not wxglade... :]

Uhm. Too many mutts. Yeah.



Re: remove x11/wxglade

2023-10-15 Thread Thomas Frohwein
On Sun, Oct 15, 2023 at 06:01:57PM +0200, Stefan Hagen wrote:
> Thomas Frohwein wrote (2023-10-15 17:26 CEST):
> > On Sun, Oct 15, 2023 at 11:18:16AM -0400, Thomas Frohwein wrote:
> > 
> > [...]
> > 
> > > +USE_NOBTCFI= Yes
> > > +USE_WXALLOWED=   Yes
> > 
> > Ignore these, it was just me blindly trying something which shouldn't
> > make its way into any potential update of the port.
> 
> I authenticated, and downloaded Blazing Sails and Q.U.B.E 2.
> Works almost as advertised.
> 
> Almost, because the games got installed to ~/Games/QUBE2 and 
> ~/Games/BlazingSails.
> 
> Portwise, maybe one or two more newlines at appropriate places before 
> committing?
> 
> OK for import sdk@

I assume the ok is for legendary, not wxglade... :]



Re: remove x11/wxglade

2023-10-15 Thread Stefan Hagen
Thomas Frohwein wrote (2023-10-15 17:26 CEST):
> On Sun, Oct 15, 2023 at 11:18:16AM -0400, Thomas Frohwein wrote:
> 
> [...]
> 
> > +USE_NOBTCFI=   Yes
> > +USE_WXALLOWED= Yes
> 
> Ignore these, it was just me blindly trying something which shouldn't
> make its way into any potential update of the port.

I authenticated, and downloaded Blazing Sails and Q.U.B.E 2.
Works almost as advertised.

Almost, because the games got installed to ~/Games/QUBE2 and 
~/Games/BlazingSails.

Portwise, maybe one or two more newlines at appropriate places before 
committing?

OK for import sdk@









Re: remove x11/wxglade

2023-10-15 Thread Thomas Frohwein
On Sun, Oct 15, 2023 at 11:18:16AM -0400, Thomas Frohwein wrote:

[...]

> +USE_NOBTCFI= Yes
> +USE_WXALLOWED=   Yes

Ignore these, it was just me blindly trying something which shouldn't
make its way into any potential update of the port.



Re: remove x11/wxglade

2023-10-15 Thread Thomas Frohwein
On Sun, Oct 15, 2023 at 10:56:12AM -0400, Thomas Frohwein wrote:
> On Sun, Oct 15, 2023 at 04:41:52PM +0200, Antoine Jacoutot wrote:
> > Hi.
> > 
> > x11/wxglade is currently broken because it does not build with new 
> > wxWidgets.
> > It depends on python2 and x11/py-wxPython which has moved to python3.
> > Nothing depends on it in tree.
> > 
> > OK to remove?
> 
> There is a newer version 1.0.5 (1.0.0 in ports) not referenced on the
> project's homepage, and the README on GitHub indicates this can work
> with python3 and is recommended [1]:
> 
> > "Requirements [..] Python (http://www.python.org) 2.7, 3.4 or later"
> 
> > "If you have a choice, you should prefer wxPython Phoenix running on
> > Python 3.x."
> 
> Not sure about the effort needed to update it, but it sounds like there
> should be an avenue for that.
> 
> [1] https://github.com/wxGlade/wxGlade
> > 
> > -- 
> > Antoine
> > 
> 

I built the update to 1.0.5, but run into a segfault with lots of gtk3
in the backtrace. With that and it having been marked BROKEN for over 6
months, I'm leaning towards removing the port now actually, unless
there is an easy fix someone can spot for the runtime, or maintainer
weighs in...

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0b5e2ab42c89 in gtk_notebook_allocate_stack ()
   from /usr/local/lib/libgtk-3.so.2201.0
[Current thread is 1 (process 461053)]
(gdb) bt
#0  0x0b5e2ab42c89 in gtk_notebook_allocate_stack ()
   from /usr/local/lib/libgtk-3.so.2201.0
#1  0x0b5e2aa14638 in gtk_css_gadget_allocate ()
   from /usr/local/lib/libgtk-3.so.2201.0
#2  0x0b5e2a9af51f in gtk_box_gadget_allocate_child ()
   from /usr/local/lib/libgtk-3.so.2201.0
#3  0x0b5e2a9ae8c7 in gtk_box_gadget_allocate ()
   from /usr/local/lib/libgtk-3.so.2201.0
#4  0x0b5e2aa14638 in gtk_css_gadget_allocate ()
   from /usr/local/lib/libgtk-3.so.2201.0
#5  0x0b5e2ab3cc01 in gtk_notebook_size_allocate ()
   from /usr/local/lib/libgtk-3.so.2201.0
#6  0x0b5dc1917c10 in g_closure_invoke ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#7  0x0b5dc19322d0 in signal_emit_unlocked_R ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#8  0x0b5dc1933642 in g_signal_emit_valist ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#9  0x0b5dc1933a15 in g_signal_emit ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#10 0x0b5e2ac903ea in gtk_widget_size_allocate_with_baseline ()
   from /usr/local/lib/libgtk-3.so.2201.0
#11 0x0b5e72980c2b in wxPizza::size_allocate_child(_GtkWidget*, int, int, 
int, int,
int) () from /usr/local/lib/libwx_gtk3u_core-3.2.so.0.0
#12 0x0b5e729810d5 in pizza_size_allocate(_GtkWidget*, 
_cairo_rectangle_int*) ()
   from /usr/local/lib/libwx_gtk3u_core-3.2.so.0.0
#13 0x0b5dc1917c10 in g_closure_invoke ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#14 0x0b5dc19322d0 in signal_emit_unlocked_R ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#15 0x0b5dc1933642 in g_signal_emit_valist ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#16 0x0b5dc1933a15 in g_signal_emit ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#17 0x0b5e2ac903ea in gtk_widget_size_allocate_with_baseline ()
   from /usr/local/lib/libgtk-3.so.2201.0
#18 0x0b5e72980c2b in wxPizza::size_allocate_child(_GtkWidget*, int, int, 
int, int,
int) () from /usr/local/lib/libwx_gtk3u_core-3.2.so.0.0
#19 0x0b5e729810d5 in pizza_size_allocate(_GtkWidget*, 
_cairo_rectangle_int*) ()
   from /usr/local/lib/libwx_gtk3u_core-3.2.so.0.0
#20 0x0b5dc1917c10 in g_closure_invoke ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#21 0x0b5dc19322d0 in signal_emit_unlocked_R ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#22 0x0b5dc1933642 in g_signal_emit_valist ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#23 0x0b5dc1933a15 in g_signal_emit ()
   from /usr/local/lib/libgobject-2.0.so.4200.17
#24 0x0b5e2ac903ea in gtk_widget_size_allocate_with_baseline ()
   from /usr/local/lib/libgtk-3.so.2201.0
#25 0x0b5e72980c2b in wxPizza::size_allocate_child(_GtkWidget*, int, int, 
int, int,
int) () from /usr/local/lib/libwx_gtk3u_core-3.2.so.0.0
#26 0x0b5e729810d5 in pizza_size_allocate(_GtkWidget*, 
_cairo_rectangle_int*) ()
   from /usr/local/lib/libwx_gtk3u_core-3.2.so.0.0
--Type  for more, q to quit, c to continue without paging--q
? SEGFAULT
Index: Makefile
===
RCS file: /cvs/ports/x11/wxglade/Makefile,v
retrieving revision 1.10
diff -u -p -r1.10 Makefile
--- Makefile27 Sep 2023 20:37:28 -  1.10
+++ Makefile15 Oct 2023 15:17:58 -
@@ -1,12 +1,12 @@
-BROKEN=does not build with new wxWidgets; needs an 
update
-
 COMMENT=   GUI designer for wxWidgets/wxPython user interfaces
 
-MODPY_EGG_VERSION= 1.0.0
+USE_NOBTCFI=   Yes
+USE_WXALLOWED= Yes
+
+MODPY_EGG_VERSION= 1.0.5
 DISTNAME=  

Re: remove x11/wxglade

2023-10-15 Thread Thomas Frohwein
On Sun, Oct 15, 2023 at 04:41:52PM +0200, Antoine Jacoutot wrote:
> Hi.
> 
> x11/wxglade is currently broken because it does not build with new wxWidgets.
> It depends on python2 and x11/py-wxPython which has moved to python3.
> Nothing depends on it in tree.
> 
> OK to remove?

There is a newer version 1.0.5 (1.0.0 in ports) not referenced on the
project's homepage, and the README on GitHub indicates this can work
with python3 and is recommended [1]:

> "Requirements [..] Python (http://www.python.org) 2.7, 3.4 or later"

> "If you have a choice, you should prefer wxPython Phoenix running on
> Python 3.x."

Not sure about the effort needed to update it, but it sounds like there
should be an avenue for that.

[1] https://github.com/wxGlade/wxGlade
> 
> -- 
> Antoine
> 



remove x11/wxglade

2023-10-15 Thread Antoine Jacoutot
Hi.

x11/wxglade is currently broken because it does not build with new wxWidgets.
It depends on python2 and x11/py-wxPython which has moved to python3.
Nothing depends on it in tree.

OK to remove?

-- 
Antoine



Re: remove x11/wxglade

2023-01-15 Thread Antoine Jacoutot
Thanks. In this case I can just temporarily mark it broken. 

—
Antoine

> On 15 Jan 2023, at 18:06, Daniel Winters  wrote:
> 
> Hi Theo,
> 
>>> Can I remove x11/wxglade?
>> 
>> Sure, unless MAINTAINER speaks up very soon.
> 
> Maintainer here: I think its best to remove it for now.
> 
> After we have a newer wxPython in the tree I will look at updating to a newer 
> version.
> 
> Cheers,
> Daniel
> 
> 



Re: remove x11/wxglade

2023-01-15 Thread Daniel Winters
Hi Theo,

>> Can I remove x11/wxglade?
> 
> Sure, unless MAINTAINER speaks up very soon.

Maintainer here: I think its best to remove it for now.

After we have a newer wxPython in the tree I will look at updating to a newer 
version.

Cheers,
Daniel



Re: remove x11/wxglade

2023-01-12 Thread Landry Breuil
Le Thu, Jan 12, 2023 at 03:22:09PM +, Stuart Henderson a écrit :
> quick notes on the other wxPython users:
> 
> : $ grep wxPython /usr/ports/INDEX | cut -d'|' -f2
> : audio/pykaraoke
> : comms/wammu
> 
> old py2-only stuff, there is a pyKaraoke on pypi but it's a different
> thing, seem to not be maintained upstream any more
> 
> : graphics/hugin
> 
> not sure (active upstream, likely to support py3)
> 
> : graphics/sk1
> 
> py2-only upstream

upstream dev passed away (per $HOMEPAGE) so even if the latter says
development is still active
https://github.com/sk1project/sk1-wx/issues/338 doesnt show much
activity. There's a py3 branch on
https://github.com/sk1project/sk1-wx/tree/py3
.. without much commits.



Re: remove x11/wxglade

2023-01-12 Thread Antoine Jacoutot
On Thu, Jan 12, 2023 at 03:22:09PM +, Stuart Henderson wrote:
> quick notes on the other wxPython users:
> 
> : $ grep wxPython /usr/ports/INDEX | cut -d'|' -f2

Yes I am taking care of wxPython and dependencies.
But working on x11/wxglade while nothing depends on it raises the usefullness
question.


> : audio/pykaraoke
> : comms/wammu
> 
> old py2-only stuff, there is a pyKaraoke on pypi but it's a different
> thing, seem to not be maintained upstream any more
> 
> : graphics/hugin
> 
> not sure (active upstream, likely to support py3)
> 
> : graphics/sk1
> 
> py2-only upstream
> 
> : math/prover9/p9m4
> 
> not sure
> 
> : print/printrun
> 
> 2.0.0rc releases support py3, need new wxPython
> 
> : x11/py-wxPython
> 
> .. (wxpython itself)
> 
> : x11/wxglade
> 
> likely to work with new wxPython
> 

-- 
Antoine



Re: remove x11/wxglade

2023-01-12 Thread Stuart Henderson
quick notes on the other wxPython users:

: $ grep wxPython /usr/ports/INDEX | cut -d'|' -f2
: audio/pykaraoke
: comms/wammu

old py2-only stuff, there is a pyKaraoke on pypi but it's a different
thing, seem to not be maintained upstream any more

: graphics/hugin

not sure (active upstream, likely to support py3)

: graphics/sk1

py2-only upstream

: math/prover9/p9m4

not sure

: print/printrun

2.0.0rc releases support py3, need new wxPython

: x11/py-wxPython

.. (wxpython itself)

: x11/wxglade

likely to work with new wxPython



Re: remove x11/wxglade

2023-01-12 Thread Antoine Jacoutot
On Thu, Jan 12, 2023 at 01:56:48PM +0100, Jeremie Courreges-Anglas wrote:
> On Thu, Jan 12 2023, Antoine Jacoutot  wrote:
> > Hi.
> >
> > Can I remove x11/wxglade?
> > Nothing depends on it and it's stuck at python2.
> 
> Is that true?  From https://wxglade.sourceforge.net/ :

Yes it's true in our tree.


> 
>2020-06-05
>wxGlade bug fix release 0.9.6 uploaded; this version is compatible
>with wxPython 4.1 and Python 3.8
> 
> I haven't looked closely but I suspect it's x11/py-wxPython that is the
> hard part to move to a 4.X release that supports python3 (alien build
> system IIRC).  wxPython 4.2.0 seems to explicitely address python 3.10
> issues.
> 
> -- 
> jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE
> 

-- 
Antoine



Re: remove x11/wxglade

2023-01-12 Thread Jeremie Courreges-Anglas
On Thu, Jan 12 2023, Antoine Jacoutot  wrote:
> Hi.
>
> Can I remove x11/wxglade?
> Nothing depends on it and it's stuck at python2.

Is that true?  From https://wxglade.sourceforge.net/ :

   2020-06-05
   wxGlade bug fix release 0.9.6 uploaded; this version is compatible
   with wxPython 4.1 and Python 3.8

I haven't looked closely but I suspect it's x11/py-wxPython that is the
hard part to move to a 4.X release that supports python3 (alien build
system IIRC).  wxPython 4.2.0 seems to explicitely address python 3.10
issues.

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE



Re: remove x11/wxglade

2023-01-12 Thread Theo Buehler
On Thu, Jan 12, 2023 at 12:00:20PM +0100, Antoine Jacoutot wrote:
> Can I remove x11/wxglade?

Sure, unless MAINTAINER speaks up very soon.

ok tb



remove x11/wxglade

2023-01-12 Thread Antoine Jacoutot
Hi.

Can I remove x11/wxglade?
Nothing depends on it and it's stuck at python2.
And also in the way of wxWidgets update.

Thanks.

-- 
Antoine