| 1 |
> On 2 Jan 2023, at 12:48, m1027 <m1027@××××××.net> wrote: |
| 2 |
> |
| 3 |
> Hi and happy new year. |
| 4 |
> |
| 5 |
> When we create apps on Gentoo they become easily incompatible for |
| 6 |
> older Gentoo systems in production where unattended remote world |
| 7 |
> updates are risky. This is due to new glibc, openssl-3 etc. |
| 8 |
> |
| 9 |
> So, what we've thought of so far is: |
| 10 |
> |
| 11 |
> (1) Keeping outdated developer boxes around and compile there. We |
| 12 |
> would freeze portage against accidental emerge sync by creating a |
| 13 |
> git branch in /var/db/repos/gentoo. This feels hacky and requires a |
| 14 |
> increating number of develper VMs. And sometimes we are hit by a |
| 15 |
> silent incompatibility we were not aware of. |
| 16 |
> |
| 17 |
> (2) Using Ubuntu LTS for production and Gentoo for development is |
| 18 |
> hit by subtile libjpeg incompatibilites and such. |
| 19 |
> |
| 20 |
> (3) Distributing apps as VMs or docker: Even those tools advance and |
| 21 |
> become incompatible, right? And not suitable when for smaller Arm |
| 22 |
> devices. |
| 23 |
> |
| 24 |
> (4) Flatpak: No experience, does it work well? |
| 25 |
> |
| 26 |
> (5) Inventing a full fledged OTA Gentoo OS updater and distribute |
| 27 |
> that together with the apps... Nah. |
| 28 |
> |
| 29 |
> Hm... Comments welcome. |
| 30 |
|
| 31 |
I'd really suggest just using stable in production and a mix |
| 32 |
for developers so you can catch any problems beforehand. |
| 33 |
|
| 34 |
We try to be quite conservative about things like OpenSSL 3, |
| 35 |
glibc updates, etc. |
Archives