After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781548 - Allow switching between native (for instance osxappinfo) and generic (freedesktop-based) appinfo implementation at build time
Allow switching between native (for instance osxappinfo) and generic (freedes...
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: build
unspecified
Other Mac OS
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2017-04-20 17:05 UTC by Mihai Moldovan
Modified: 2018-05-24 19:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Appinfo implementation switching (5.04 KB, patch)
2017-04-20 17:21 UTC, Mihai Moldovan
none Details | Review
Refreshed version of Mihai's patch, now for 2.56.0 (4.88 KB, patch)
2018-05-11 15:58 UTC, Ryan Schmidt
needs-work Details | Review

Description Mihai Moldovan 2017-04-20 17:05:33 UTC
This patchset lets users select the appinfo implementation at build time.

The native OS X (appbundle-based) appinfo implementation is not good enough for all cases. Especially when using GTK+ compiled against X11, having the generic appinfo implementation is more useful.

Also, I have fixed up installing missing headers for the win32appinfo implementation and made that switchable as well - even though the generic appinfo implementation currently won't work on Windows.

The default behavior is retained - by default glib will select the native appinfo implementation as before if the new configure switch is not passed.
Comment 1 Matthias Clasen 2017-04-20 17:13:48 UTC
No patches ?

I think I've outlined my view of this before (maybe in some other bug): I think this is stopgap measure that we should perhaps merge to keep all those rebuilders (brew and friends) from patching glib.

But it is really not more than just that: a stopgap. What we need here is to

1) make the implementation of the extension point runtime-selectable

2) support multiple implementations, merging their appinfo sets together. There will be some interesting questions to answer here, like: how to resolve defaults
Comment 2 Mihai Moldovan 2017-04-20 17:21:17 UTC
Created attachment 350155 [details] [review]
Appinfo implementation switching
Comment 3 Mihai Moldovan 2017-04-20 17:22:07 UTC
I had to create the bug first to get its ID and reference that in the commit. :)
Comment 4 Mihai Moldovan 2017-04-20 17:23:19 UTC
Yes, runtime selection with multiple implementations would be even better, but as a packager being able to switch implementations via a configure option is much better than patching glib around.
Comment 5 Daniel Macks 2017-04-23 20:48:47 UTC
Seems like this will help resolve Bug 780309 also.
Comment 6 Ryan Schmidt 2018-05-11 15:58:40 UTC
Created attachment 371942 [details] [review]
Refreshed version of Mihai's patch, now for 2.56.0
Comment 7 Philip Withnall 2018-05-16 09:13:36 UTC
Review of attachment 371942 [details] [review]:

Can you please rebase this against master and submit it as a git-formatted patch? Anything else makes it harder to deal with the contributions.

This will also need equivalent support in the Meson build system, as we’re at a stage where we want feature parity between the two build systems.

Thanks.
Comment 8 GNOME Infrastructure Team 2018-05-24 19:30:16 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1263.