Christopher Nielsen
Christopher Nielsen
Ryan, are you fine with merging this?
> _If_ this gets merged after packages are built it then needs a bump to the workaround so it install 1.10.0. Dean, can you clarify what needs a bump?
Rebased against master, and fixed the merge conflict.
> Rebased against master, and fixed the merge conflict. Okay, now that the merge conflict has been resolved, where do things stand? @chrstphrchvz do your concerns relative to Perl still...
Resolved the merge conflict via GitHub GUI, adding a commit. So ultimately we'll want to squash.
I'd prefer this to be an opt-in option, enabled via a new parameter. This is similar in spirit to optional "strict" mode, used in some CMake (and/or Configure) scripts.
> > In terms of sharing the data and logic, can the MacPorts infrastructure scripts utilize MacPorts base? > > Sure. That has the (perhaps minor) drawback that it can...
After still more reflection, I've come to a key realization: License info rarely changes. So while it would be nice to source that data from the `_resources` area, baking it...
> Not sure our QA/CI goes back far enough to verify that this PR will work on older macOS, but it should since it adds back the changes that removed...
> ``` > :info:configure -- Looking for C++ include filesystem > :info:configure -- Looking for C++ include filesystem - not found > :info:configure -- Looking for C++ include experimental/filesystem >...