From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A306815800F for ; Mon, 2 Jan 2023 12:48:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5C23EE0903; Mon, 2 Jan 2023 12:48:40 +0000 (UTC) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1861AE0896 for ; Mon, 2 Jan 2023 12:48:39 +0000 (UTC) Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id DE4E7240224 for ; Mon, 2 Jan 2023 13:48:37 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1672663717; bh=S5iU4DEdM9GGLYBq051Y0PqviXO6Yt9He1Wq4Awdhk0=; h=Date:From:To:Subject:From; b=axB88/rJ8ylUj2GMF8aE6IyFgTyKtkWvjUonNpOCdmZi9kIL4pRzufSn4Tn8Znd99 czvrl0wb4qb2BCRFQj/QBFfIOgg0e823fDPPRYwBwiO+ACRPVhs6jffCcyZLprzjJJ MhoVQVmt9TklC7SoJkAVuvCGD/080Uz455nNuqTvMF9p7fh7Vh2Wq4hAGeYHPKAGqV uhJzR+pIy8+MryuePZhz/YYBHhKlyQ+iRP1a9BEI5JAQZUENVq2Igpo/Iy9Xiru1JU n0wes8d5FD0Py8O219jgpndvH6ywpQkqlN4oC2BZGvq5x9vfII/zPXUwIWZZLWYbK+ CGMphgsJAW/tg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Nlwdx41zqz6tnM for ; Mon, 2 Jan 2023 13:48:37 +0100 (CET) Date: Mon, 2 Jan 2023 12:48:36 +0000 From: m1027 To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] Gentoo LTS or: proper backward compatibility? Message-ID: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Archives-Salt: 86f94a5e-b3bf-410a-b566-7e29776dd44d X-Archives-Hash: ab6488cb0f08f1e83e214a057c2df038 Hi and happy new year. When we create apps on Gentoo they become easily incompatible for older Gentoo systems in production where unattended remote world updates are risky. This is due to new glibc, openssl-3 etc. So, what we've thought of so far is: (1) Keeping outdated developer boxes around and compile there. We would freeze portage against accidental emerge sync by creating a git branch in /var/db/repos/gentoo. This feels hacky and requires a increating number of develper VMs. And sometimes we are hit by a silent incompatibility we were not aware of. (2) Using Ubuntu LTS for production and Gentoo for development is hit by subtile libjpeg incompatibilites and such. (3) Distributing apps as VMs or docker: Even those tools advance and become incompatible, right? And not suitable when for smaller Arm devices. (4) Flatpak: No experience, does it work well? (5) Inventing a full fledged OTA Gentoo OS updater and distribute that together with the apps... Nah. Hm... Comments welcome. Thanks