Joshua Root
Joshua Root
Do we actually need to do this at all on OS versions capable of hfscompression?
But if base is outdated, the message indicating that is still printed after updating the ports tree? Isn't that less consistent?
It's not safe to do anything but exit after updating base. So yeah, the operations happen in the order they do for good reasons.
Not really, as we don't know whether it's safe to run portindex until we know if base is about to be updated.
We don't sync first because of this: https://trac.macports.org/ticket/30739 Yes the same would happen if the user just runs `port sync` when base is outdated, but selfupdate can avoid that, which...
Sure, if we can adjust the messages to reduce confusion that would be good. The phrasing could use some workshopping as you say. Another solution that would require more work...
It was intentional to default to not using a `-stdlib` option at all on non-darwin platforms, because it's only on macOS that being able to use a stdlib other than...
I'm not quite sure what Ryan is getting at, but if there are ports that don't handle an empty cxx_stdlib correctly, they should probably be fixed regardless.
Empty is a valid value. Portfiles need to be able to handle it either way. > On all platforms, clang has the ability to use either libstdc++ or libc++, and...
> instead of adding workarounds to every usage of this in a Portfile? Are there many ports looking at this variable? If so, a better question would be why they...