I want to compile new versions of openssl, bash, and similar unix tools in the same way that Apple would. I want to link against the OS's built-in libraries where possible, and I want to copy the resulting binaries into
/usr/bin, replacing what Apple ships with OS X.
I am aware that this is usually a terrible idea, for two reasons:
- An OS X update might reinstate Apple's binaries, undoing your work and leaving your system in an unknown state.
- Some software may depend on the specific behavior of Apple's binaries.
Instead, it is generally recommended that mac users install custom binaries alongside Apple's system binaries. Both homebrew and MacPorts operate under this principle.
However, I'm running Mavericks, which will never receive another software update from Apple. The Apple binaries on my system have known security vulnerabilities, which IMO outweighs theoretical compatibility concerns.
Is there a standard way to go about this, or would it be different for every program? Can I somehow leverage parts of e.g. the MacPorts project to make the process easier, or do I need to install all compilation dependencies from scratch?
If this just isn't realistically feasible, I'd like to know that too.