[MacPorts] #69919: Nautilus upgrade + extra new ports tracker-3.0, tracker-miners and glib2 fix to include gio-launch-desktop bin.
MacPorts
noreply at macports.org
Sun Jul 7 05:01:51 UTC 2024
#69919: Nautilus upgrade + extra new ports tracker-3.0,tracker-miners and glib2 fix
to include gio-launch-desktop bin.
-------------------------------------------------+-------------------------
Reporter: christophecvr | Owner: (none)
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.9.99
Resolution: | Keywords: gnome
Port: nautilus tracker-3.0 tracker-miner | nautilus
glib2 nautilus-python |
-------------------------------------------------+-------------------------
Comment (by christophecvr):
Replying to [comment:10 cooljeanius]:
> Replying to [comment:9 christophecvr]:
> > In one file and use that it (could ??) be possible to build a glib2
who can be used with x11 or quartz backend. This would solve a lot and be
very good for for example the ticket :
> >
> > #60511
> >
> > @cooljeanius do you still follow this ?
> >
>
> Yeah but the specific instances of it that I'm most concerned about at
this moment are #70274 and #63680
>
Hi I checked those tickets. So there was a try to have two glib2 versions
one with quartz and one with x11 support build together ? \\
Then also 2 gtk3 versions one with x11 and one with quartz support ? \\
I'm not sure but if a single glib2 build to support x11 and quartz could
be build it already would be a good step forward. \\
I'm prepared to investigate and try it out here. since looks that it
should be possible to merge the functions used into header files : \\
{{{
gosxappinfo.m
# and
gdesktopappinfo.h
}}}
Into a new header file that supports the osxappinfo and gdesktopappinfo
specific function calls. Then when a application uses x11 backend it will
use the specific functions of gdesktopapp quartz those of osxappinfo.
then build glib2 that support generic and native in one.
There also should not be problems with not find symbols on build time and
if at some point we come to a duplicate symbols error it is just a point
to trac the source and mostly change the double declarations by changing
one of them to ext.
Think it's worth to try that out ?
--
Ticket URL: <https://trac.macports.org/ticket/69919#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list