Hi, On Mon 02 Jan 2023 23:31:17 GMT, m1027 wrote: > I am not complaining here. Hey, we are on rolling release. Some of > you may even know individual solutions to work around each of it. > However, we just may get into trouble when distributing newly > compiled apps (on new Gentoo systems) to older Gentoo systems. And > we don't know in advance. I am looking for the best way to avoid > that.
It’s not really a production environment, but I have this hobby infra I’ve set up when I was a student an my solution is to have a VM compiling the big packages (gcc, glibc, llvm, php, etc.) and publish a binary repo from that. Then, every VM pulls this, and compile what’s specific on top of that. Everything is handled by crons. So far it works. One thing to get in mind is that, if a VM got stuck to an old commit (e.g. because one package needed a use change and emerge fails to update world due to that), I’m always re-compiling everything, because I’m scared of glibc or ncurses ABI breaks. My scale is ~30 VMs on 4 physical servers. -- Alarig
