Mesa dependency in gtk3

[Clemens Lang]

On Fri, Oct 18, 2024 at 09:40:22PM +0200, Vincent Habchi wrote:
> > In other words, when libepoxy is built in an environment where mesa is
> > available, its pkg-config file will reference it. If mesa isn't
> > installed while libepoxy is built, gtk3 will configure fine. If it is
> > installed, gtk3 configure will fail when mesa is not installed.
> 
> You mean that if you have mesa installed when you build libepoxy, but
> then discard it before you install gtk3, gtk3 will fail, right? If
> this is what you mean, the question is, who does that?

I would guess everybody that had gtk3 installed when it still had a
dependency on mesa and has been upgrading from that ever since without
cleaning up unused ports.

Alternatively, there are about 74 other ports that depend on mesa, users
might have one of those installed.


> > fixed, we should keep the build dependency in gtk3, because a broken
> > build is a bad user experience, and a build-time dependency isn't
> > the end of the world.
> 
> While I agree with the first term, I don’t with the second. I like to
> keep my dependencies at an absolute minimum, and especially with x11.
> But, of course, your mileage may vary :)

I sympathise with this goal, but we should leave those users out in the
rain that still have mesa installed, or have mesa installed because of a
different dependency.

This would be less of a problem if trace mode worked on arm64, but it
currently doesn't. There was an interesting idea in the corresponding
ticket recently that I want to implement when I find time — then we
could just recommend using trace mode instead when these things happen.

-- 
Clemens