[Geany-Devel] Future removal of Geany-Plugins from Fedora

[Matthew Brush]

On 2016-11-11 03:24 PM, Matthew Brush wrote:
> Hi All,
>
> I was seeking help for some issue for the Markdown plugin with WebKitGtk
> today on IRC and someone pointed out this issue with Fedora:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1375807
>
> Basically the whole Geany-Plugins package will be removed since one of
> the plugins uses an older version of a library that will be removed from
> Fedora.
>
> IMO, it would be wise to separately package plugins to prevent one
> outdated plugin from getting the others removed. AFAIK this is how it's
> packaged on Debians.
>

Actually according to the mailing list post (with a quite annoying tone) 
linked from the bug report, it lists:

	geany-plugins-devhelp-0:1.27-1.fc24.x86_64
	geany-plugins-geanypy-0:1.27-1.fc24.x86_64
	geany-plugins-markdown-0:1.27-1.fc24.x86_64
	geany-plugins-webhelper-0:1.27-1.fc24.x86_64

So perhaps Fedora does package them separately? The fellow on IRC said 
all of Geany would be removed, so I'm a little confused. Also I'm not 
sure why GeanyPy is listed, it doesn't use Webkit at all and Devhelp 
plugin uses it indirectly through libdevhelp.

The other thing is that none of the plugins really use general WWW 
untrusted code, but rather just whatever the user is working on (ie. 
Devhelp docs, HTML generated from Markdown, their own HTML files). I 
guess these are more "special flowers" as the OP so politely put it.

Anyway, we could indeed upgrade to the newer version if we want to 
re-write the affected plugin code, drop gtk2 support and stop being able 
to work on Windows. Probably using conditional compilation to support 
both is the way forward for the immediate future. I guess for Fedora, 
they'll have to either enable GTK3 build (and lose a bunch of unported 
plugins) or stay with GTK2 build (and lose any old Webkit-using plugins).

Regards,
Matthew Brush