Less than a problem with ccache, and OpenBSD solved the time_t issue long ago.
But sometimes I envy common lispers, you livepatch any crap like nothing. Also, 9front: megafast system recompilation so the worst of the issue would be rebooting a machine.
> OpenBSD solved the time_t issue long ago.
It's amazing how quickly you can solve problems when you're fine breaking user space between releases.
Not that Linux has a perfect record, but it's much harder when you actually try.
I'd prefer to refer to it as 'changing userspace', as opposed to breaking it. The ABI is changed, and userspace/ports are updated to use the new ABI. Users just upgrade as usual, and don't see any 'breakage'. It wouldn't work for Linux, because the kernel and glibc + the rest of userspace are developed separately.
Slides on OpenBSD's transition to 64-bit time_t
https://www.openbsd.org/papers/eurobsdcon_2013_time_t/index....
"I have altered the ABI. Pray I do not alter it further." -- Theo de Raadt
loading story #40267624
Upgrading is not an issue, now you have vmd and a lot of mirrors still have both the old TGZ sets, ramdisks, kernels and packages to be able to virtualize old machines just in case.
loading story #40267531