+.include "../../x11/wxGTK/wxGTKversion.mk"
+.include "${WXGTKPKGSRCDIR}/buildlink3.mk"
It would seem better to have a way to express which versions are ok and
then just include a wxGTK file and have that do everything.
There are a lot of things in mk/foo.buildlink3.mk like this.
Then there is /usr/pkgsrc/lang/python, which isn't a package but
collects lots of makefile fragments.
My understanding is that a system can really only have one wxGTK
installed at a time.
So I would lean to:
create mk/wxGTK.mk
have it ?= a user-settable version variable, defaulting to 28 or 30
let the user set the variable in mk.conf if wanted
packages declare WXGTK_VERSIONS_INCOMPATIBLE
building fails if the chosen list is in the INCOMPATIBLE LIST
and just let it be at that, even though in theory something more
complicated could allow binary packages of more things, even if they
couldn't be installed at once.
My impression is that most things work with 28, and somewhat fewer with
30, but that it's a bug for any package (upstream) if it doesn't work
with 30. But I'm not 100% clear on that. Is that how you see it?
Attachment:
signature.asc
Description: PGP signature