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