what's with the C++ <filesystem> extension?

[Chris Jones]

> On 19 Sep 2022, at 11:53 am, René J.V. Bertin <rjvbertin at gmail.com> wrote:
> 
> On Sunday September 18 2022 23:57:53 Chris Jones wrote:
> 
>> Follow the above at your own risk.
> 
> As I said, there is no need to update the system libc++ on systems that already have it; `port:libcxx` can (could) provide a set of libraries under ${prefix} that override the system ones for dependent ports, just like any other port that provides newer versions of what's also provided by Apple.
> This carries the same amount of risk as comes with those other ports (port:zlib, for instance...)

No, its completely different to ports like zlib. There has to be a single runtime everything uses. Having some ports built against the system runtime and others using a newer macports provided one is a recipe for problems when you then try and combine these. That is precisely why the port works the way it does and not how you seem to think it should.

But anyway, I m sure you will think you are right, so please feel free to experiment on your own system, as you get to own the pieces there once it breaks.

> 
>> 
>> The much better solution, imho, is if you needed newer c++ support, just migrate to a more recent os that supports it…
> 
> Yeah, sure. Let's see before I download the 10.15 installer, oh, wait, my hardware will only upgrade to 10.13 (officially).
> 
> Guess why I'm migrating away from Macs ...
> 
> R.