Re: dte: darwin doesn't get X11-specific files

[Jason Bacon <jtocino%gmx.com@localhost>]

On 1/3/24 11:15, Greg Troxel wrote:
> Jason Bacon <jtocino%gmx.com@localhost> writes:
>
> > XQuartz (X11 server for Mac) works pretty well, but the situation is
> > less than awesome.  It takes a while to fire up the X11 server
> > on-demand, and it provides a UI that's inconsistent with the Mac
> > interface.  There have also been numerous bugs over the years that have
> > caused some X11 apps not to function.
> >
> > Institutionally-managed Macs may not have XQuartz installed and it can
> > be a headache to request it.  I.T. departments are defensive by nature,
> > and hesitant to roll out software they're not familiar with.  Those
> > fears are often well-justified, as it takes a lot of resources to deal
> > with surprises.
> >
> > It's probably best to assume that Mac users don't have X11.
>
> Sure, but that leads to
>
>    have an x11 option
>
>    have the x11 option require x things
>
>    default the option on, except on macs
>
>
> It definitely does not lead to a PLiST.notdarwin!

Maybe I should have been clearer.  I was referring to upstream
assumptions about availability of an X11 server (in response to "I think
it's a bug for them (upstream) to assume that darwin means not x").

As an upstream developer, I would not generally expect or require Mac
users to have an X11 server to run my software.  It's not the norm for
Mac users.  Note that Qt apps can utilize both Mac's native GUI and X11,
which is one of the reasons I would lean toward using it.  This way, I
can support both native Mac and X11 users without duplicating the UI.

As a pkgsrc developer, I would support X11 functionality wherever
possible, which yes, might require an option in the package as you stated.