WrapEarnPass left a comment (geany/geany-plugins#1570)
geany and geany-plugins are building to entirely different specs.
I checked out geany at 2.1.0 to see what it was building to.
autogen reports
```checking for gtk+-3.0 >= 3.24 glib-2.0 >= 2.56 gio-2.0 >= 2.56
gmodule-no-export-2.0 gthread-2.0... yes```
geany-plugins@master is waaaay behind that.
```
checking for gtk+-3.0 >= 3.0
glib-2.0 >= 2.38
gio-2.0 >= 2.30
gdk-pixbuf-2.0 >= 2.0
webkit2gtk-4.1 >= 2.18
gthread-2.0... no
```
I know they are separate projects, but allowing a very closely integrated
project like geany-plugins to allow for such a wide drift means anyone who
builds plugins themselves may end up with a ABI near-match, which is MUCH worse
than a miss.
Miss, fail fast, can't build until you upgrade your build environment.
Near-match, builds, dev thinks it's valid, user does too until it randomly
crashes somewhere. Spends hours troubleshooting, gets frustrated and starts 3AM
angry posting about the craptitude of the software.
I don't know anything about automate, and the resources available are
crepulated with AI now.
If this was a cmake project, I'd submit a pull request with a fix. I need help
if this is to be addressed.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1570#issuecomment-4929228855
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1570/[email protected]>
