Evince bundles the whole libgd just so it can consume a two line cell renderer for its icon view. In this case, it might be worth just copy-pasting this specific class and drop the libgd dependency.
Sounds worth it setting up an Initiative* to coordinate the port away from libgd. * https://gitlab.gnome.org/GNOME/Initiatives On Tue, Jun 15, 2021 at 11:59 AM Alexander Mikhaylenko via desktop-devel-list <desktop-devel-list@gnome.org> wrote: > > As far as I know, libgd is pretty much only used for tagged entries > nowadays. In GTK4 it's a lot easier to implement them in-tree than it > was in GTK3, gtk4-demo even has an example. > > On 15/06/2021 14:54, Allan Day wrote: > > Emmanuele Bassi via desktop-devel-list <desktop-devel-list@gnome.org> wrote: > > ... > >> - nautilus > >> - evince > >> - totem > >> - gnome-photos > >> - gedit > > In terms of the platform, we're working to consolidate around > > libhandy/libadwaita. That's what the new HIG documents, and is what > > we're trying to constrain ourselves to on the design side. So it would > > be interesting to know what these apps are using libgd for, and > > potentially track what needs to be done to migrate them away from it. > > I think that it would be beneficial to have our core apps use the same > > platform that we make available to 3rd parties. > > > > > > Allan > > _______________________________________________ > > desktop-devel-list mailing list > > desktop-devel-list@gnome.org > > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
