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 4D7CC1382C5 for ; Fri, 12 Jun 2020 14:00:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CDA3CE091D; Fri, 12 Jun 2020 14:00:31 +0000 (UTC) Received: from mail-qv1-f68.google.com (mail-qv1-f68.google.com [209.85.219.68]) (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 274F3E0908 for ; Fri, 12 Jun 2020 14:00:30 +0000 (UTC) Received: by mail-qv1-f68.google.com with SMTP id ec10so4387837qvb.5 for ; Fri, 12 Jun 2020 07:00:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:reply-to:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=TuPpOk4ZUURcwpWZ57hcuLXoZC5CZ0PanWJZ75h+uTs=; b=suV3P6LeALm3DsKH6mA5oD3GMS5Mu2SaN7wKr5xNiEmkb/ZJ2apEG39s+7WzTJsT+X 9IRKDJ4OvQp0eKBX7t5saKnJ10LH1rL36HVwhdH41lN6JrMWhhMypTAUNDXG7SGJe0Nx 5tG5ZHZcb1d7sbkprBWgJsRg8afz280jXBiaroRhkFq5kUeSagFrMbSdphuYjeB4s5B4 hL1K19HuZcVJH/qBd9GQ2uFHzeJSQMj8HTnU7Aio3xBZB+FCPHDPT2bRlsgH6YZgItPh bhLDbQaH3V7X15ns5959MAF8hz9GDFmjJKnfrkdU2DvmkpiPntjWUXGqr5Moms7aVd9p fq/Q== X-Gm-Message-State: AOAM5305mgnWa2BxX0aOhCdQiWK+YQvL5u/B0HNVaeg2SdM7tY2/oA97 Ae0M8GFajMWF48iZQUPozqswWK+iEsU= X-Google-Smtp-Source: ABdhPJzSwA6MTzGntggjj2gVFya0gjRUPRcjDPuH5nw2vQNLgalFXUV0AQNT3em41af3XVPlLcfRKg== X-Received: by 2002:ad4:5508:: with SMTP id az8mr12848361qvb.92.1591970429650; Fri, 12 Jun 2020 07:00:29 -0700 (PDT) Received: from [192.168.1.18] (c-76-23-130-96.hsd1.ct.comcast.net. [76.23.130.96]) by smtp.gmail.com with ESMTPSA id x43sm4877175qtk.70.2020.06.12.07.00.26 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 12 Jun 2020 07:00:29 -0700 (PDT) Subject: Re: [gentoo-user] "masked by: EAPI 7" trying up update "portage" - how to proceed To: gentoo-user@lists.gentoo.org References: <9ed9c401-7066-9c6d-8ce4-2ee94a1b903e@web.de> <20200611091031.770b9102@digimed.co.uk> <53e40310-7ee0-a3a1-d500-ed0b81c10bf4@web.de> <621b4819-e581-51a3-44e3-3bee51814d5d@web.de> <449dd2b0-356b-0bf5-7a08-8b1407ce7c17@web.de> From: Jack Message-ID: <1c440e09-c19b-0149-058b-21030a4bac8a@users.sourceforge.net> Date: Fri, 12 Jun 2020 10:00:25 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 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 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US-large X-Archives-Salt: eed2bc2a-4992-4c19-8d65-52dcc918bdb3 X-Archives-Hash: bcd78982ecbbd82993a76b0dbd466aff On 6/12/20 9:49 AM, Rich Freeman wrote: > On Fri, Jun 12, 2020 at 4:00 AM n952162 wrote: >> On 2020-06-12 08:40, n952162 wrote: >> >>>> BTW, is it becoming clear why it is best to update Gentoo at least >>>> ever few months? :) >>> Well, yes, but it's really pretty onerous. If you have gentoo in >>> embedded systems, you've got to spend considerable administrative effort >>> in each one just maintaining the status quo. >>> >>> I mean, there's no competition to gentoo, of course. But a design goal >>> could be to have a one-step sync, of some sort. >> Maybe one way to work in that direction would be to have regular - say, >> yearly - "releases", kind of like other distributions do, but on an >> ebuild basis, re-establishing a common base point. > Well, you already can just use a snapshot of the repository from any > date in time, though things like patches might not be mirrored any > longer so that isn't a perfect solution. > > Ultimately if there was enough interest in something like this the > solution would probably be another distro that just repackages Gentoo > in a release-based format. Release-based distros have their pros and > cons, but they're definitely a better fit for some problems. > > One of the issues with Gentoo is that it is fairly niche and so you > don't have the manpower to support 47 forks. With Debian you have a > bazillion derivatives - half of them are just bundling a different set > of default packages. Ubuntu has a Desktop and Server version of the > distro, and they also have flavors for various desktop environments. > Gentoo basically has just barely enough manpower to support having > Gentoo. We try to accommodate as much choice as possible in how it > gets used which is why this model works as well as it does. However, > we can't support having a Gentoo flavor that is GPL-only, or GPL-free, > or FOSS-only, or no-systemd-in-the-repo, or initial install optimized > for people who read braille. You can actually tailor Gentoo towards > just about any of those directions with some config file tweaks, but > you can't just pick the one of 300 iso images that most closely fit > your needs and run the autoinstaller and forget about it. What about some sort of tagging?  Not bundling or packaging, just occasional (quarterly?) labels, with a matrix indicating how difficult it would be to upgrade.  A hint to folks who tend to update less often than they should.  A "heads up" that things added or upgraded in the past quarter are going to be very difficult to do if you are starting with something more than three/five/...? quarters older than that.  Of course, I suppose if you read the news items as they are released, then you should have a pretty good idea of which of them are likely to bite you if you wait too long.