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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 98D4C1382C5 for ; Sun, 21 Jun 2020 21:08:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7B032E0908; Sun, 21 Jun 2020 21:08:28 +0000 (UTC) Received: from mail-ed1-f41.google.com (mail-ed1-f41.google.com [209.85.208.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2DE55E0866 for ; Sun, 21 Jun 2020 21:08:28 +0000 (UTC) Received: by mail-ed1-f41.google.com with SMTP id t21so11996086edr.12 for ; Sun, 21 Jun 2020 14:08:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=AWrFb3DTx0xoKIU4aQ9XfLwHiuK7dQh3MqLYVRk2XFE=; b=ZNx8GQWokBnpM1tc6Ag2SHnkhCz8hkapkbSdAJ13HGe1sy0uCE8Jbtzn+4CfTcDwz/ TFCa6AViGSwT1CUpBsOoPcZ+GhGEvBs4KmeIYfVgqj6OqUsbKPYg4GVQwldOMhUBmjtf nBVSHtd0li7qUFqICyHzV+mGVpiDFt1oxh9FBZBCJiQ5sLhfQE3mmNy1cn403gYkvQ0z vjnUXhfeXd/YOA5EwMely7K16iM4YMc98SyhHJPQVeXH30wRPeQpAhgZSREtTmHfwV/n zk960ggg24TH0CZ6J5NqjfMFwAqVyD9VtLGYna8y2QI4p30KUorGhku3+D/CHzYC01U4 7kVQ== X-Gm-Message-State: AOAM5309J+nFx2pn4ReHRTUhu+TEKRYTdO5rd+Qvn8Mt47rNaCxEcHgW 6oEUZd5DCp90xE1AdWP8OzYhwPRasF2hp22aiizbtRh4 X-Google-Smtp-Source: ABdhPJzTFNIu7tA5eiesRuRTZhNhBjyVr2gnF/n+y3ByQTHQr8056gEIK+099Fm6fA5DFLBUP9KRuxatY12LwQYQrBM= X-Received: by 2002:a50:a661:: with SMTP id d88mr14197612edc.34.1592773706412; Sun, 21 Jun 2020 14:08:26 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <2061dce3-a6b3-31a7-aed0-c08487fa15ce@apteryx.fr> In-Reply-To: <2061dce3-a6b3-31a7-aed0-c08487fa15ce@apteryx.fr> From: Rich Freeman Date: Sun, 21 Jun 2020 17:08:14 -0400 Message-ID: Subject: Re: [gentoo-user] Gentoo chroot with old glibc To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Archives-Salt: b75b445e-193c-4490-af85-abf8f0afc885 X-Archives-Hash: be199a063b1e876e36854d2e4e6ec978 On Fri, Jun 19, 2020 at 5:19 PM Herv=C3=A9 Guillemet wrote: > > Or do you have any suggestion for alternatives to this gentoo chroot ? > (I'd prefer avoid installing some CentOS or Ubuntu as virtual guests). You're of course free to do it any way you wish, but if I wanted to create packages for various distros, I'd probably just follow their instructions for doing so. If you're making Ubuntu 16.04 packages I suspect it would be just a lot less fuss all around to do it from an Ubuntu 16.04 container, and so on. And if you're just building binaries and creating tarballs with them, well, why? If people want to manually deal with stuff the source is already fine. If they want the benefits of a package manager they're going to want packages. And if you're hoping to encourage distros to do the packaging for you, they're probably only going to do that from source anyway. I imagine most distros have a fairly straightforward packaging system, and I suspect a lot of CI systems have plugins to churn out packages for them automatically. So why maintain some Gentoo chroot and carefully curate every single library on them to match some entirely different distro? You're going to run into stuff where Gentoo doesn't have the version you need in the repo, and you'll be fighting auto updates, and so on. But, sure, you can get Gentoo to install whatever you want as long as you don't mind manually picking packages, or maintaining your own repo where you carefully curate this stuff. --=20 Rich