Re: Any particular reason the gtk2 build was dropped from libfm-gtk2 (int included both gtk2 and gtk3)

[Robin Candau]

On 10/22/25 11:26 AM, David C Rankin wrote:

All,>

  The latest update to libfm-gtk2 renames it libfm-gtk3 but make is conflict with existing libfm-gtk2. https://gitlab.archlinux.org/archlinux/packaging/packages/libfm/-/ commits/main?ref_type=HEADS

The libfm-gtk2 package included both gtk2 and gtk3 file manager builds. Now we are left with only gtk3. It was quite convenient for old apps that use the gtk2 functionality.   Why did the gtk2 build get dropped? It was working quite nicely with the gtk3 filemanager files, posed no conflict and no additional work. Yes, it's old, but so are a lot of things that work quite well. If there weren't build failures, what was the reason behind the change?

Hi,


See the related ToDo opened in 2020 [1]

[1] https://archlinux.org/todo/gtk-2-eol/

--
Regards,
Robin Candau / Antiz

We are generally aiming toward dropping gtk2 altogether (as it reached its end of life a few years ago).

OpenPGP_0xFDC3040B92ACA748.asc
Description: OpenPGP public key

OpenPGP_signature.asc
Description: OpenPGP digital signature