Should xorg-server should be made a dependency of some key x11 component, so
that when people install an x11 application, xorg-server installs and it
actually works for them “out-of-the-box”.
For example, CherryTree is apparently a very popular gtk application, and there
was some pressure for t
Hi,
Personally, I would say yes, this makes sense given the current state of
XQuartz.app
cheers Chris
> On 20 May 2020, at 2:30 pm, Ken Cunningham
> wrote:
>
> Should xorg-server should be made a dependency of some key x11 component, so
> that when people install an x11 application, xorg-se
On 20/05/2020 15.30, Ken Cunningham wrote:
> Should xorg-server should be made a dependency of some key x11 component, so
> that when people install an x11 application, xorg-server installs and it
> actually works for them “out-of-the-box”.
I doubt even with the dependency it will not work "out of
> On 20 May 2020, at 3:55 pm, Rainer Müller wrote:
>
> On 20/05/2020 15.30, Ken Cunningham wrote:
>> Should xorg-server should be made a dependency of some key x11 component, so
>> that when people install an x11 application, xorg-server installs and it
>> actually works for them “out-of-the-bo
On May 20, 2020, at 08:30, Ken Cunningham wrote:
> Should xorg-server should be made a dependency of some key x11 component, so
> that when people install an x11 application, xorg-server installs and it
> actually works for them “out-of-the-box”.
>
> For example, CherryTree is apparently a v
On Wed, 20 May 2020, Ryan Schmidt wrote:
On May 20, 2020, at 08:30, Ken Cunningham wrote:
Should xorg-server should be made a dependency of some key x11
component, so that when people install an x11 application, xorg-server
installs and it actually works for them “out-of-the-box”.
For examp
On May 20, 2020, at 21:09, Fred Wright wrote:
> On Wed, 20 May 2020, Ryan Schmidt wrote:
>> On May 20, 2020, at 08:30, Ken Cunningham wrote:
>>
>>> Should xorg-server should be made a dependency of some key x11 component,
>>> so that when people install an x11 application, xorg-server install
> What I'm trying to avoid is having to add boilerplate code to hundreds of
> ports. So I guess that means yet another portgroup to do this. But even that
> -- editing hundreds of possibly optionally X11-using portfiles to insert the
> inclusion of that portgroup only when X11 is actually going