From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "masked by: EAPI 7" trying up update "portage" - how to proceed
Date: Fri, 12 Jun 2020 15:38:28 +0100 [thread overview]
Message-ID: <2027654.irdbgypaU6@lenovo.localdomain> (raw)
In-Reply-To: <1c440e09-c19b-0149-058b-21030a4bac8a@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 3193 bytes --]
On Friday, 12 June 2020 15:00:25 BST Jack wrote:
> On 6/12/20 9:49 AM, Rich Freeman wrote:
> > On Fri, Jun 12, 2020 at 4:00 AM n952162 <n952162@web.de> 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.
Perhaps I misunderstand this, but isn't it as simple as booting off a LiveCD/
USB, chrooting, changing profiles, cleaning up world file and letting rip with
a full 'emerge -e' @system, followed by @world for good measure?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-12 14:39 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 6:47 [gentoo-user] "masked by: EAPI 7" trying up update "portage" - how to proceed n952162
2020-06-11 8:10 ` Neil Bothwick
2020-06-11 12:47 ` Rich Freeman
2020-06-11 19:36 ` n952162
2020-06-11 20:01 ` Rich Freeman
2020-06-11 20:10 ` n952162
2020-06-11 21:05 ` Jack
2020-06-11 21:10 ` n952162
2020-06-11 21:22 ` n952162
2020-06-11 21:59 ` Jack
2020-06-11 22:05 ` n952162
2020-06-11 22:43 ` Jack
2020-06-12 6:32 ` n952162
2020-06-14 7:01 ` n952162
2020-06-14 16:02 ` antlists
2020-06-14 18:22 ` n952162
2020-06-11 21:06 ` Rich Freeman
2020-06-11 21:15 ` n952162
2020-06-11 20:28 ` n952162
2020-06-11 20:35 ` Rich Freeman
2020-06-11 20:43 ` n952162
2020-06-11 21:20 ` Rich Freeman
2020-06-11 21:45 ` n952162
2020-06-11 22:09 ` n952162
2020-06-11 23:09 ` Rich Freeman
2020-06-12 6:40 ` n952162
2020-06-12 8:00 ` n952162
2020-06-12 13:49 ` Rich Freeman
2020-06-12 14:00 ` Jack
2020-06-12 14:38 ` Michael [this message]
2020-06-12 14:42 ` J. Roeleveld
2020-06-12 14:48 ` n952162
2020-06-12 14:53 ` Rich Freeman
2020-06-12 14:50 ` Michael
2020-06-12 14:44 ` n952162
2020-06-12 14:52 ` Michael
2020-06-12 17:15 ` Peter Humphrey
2020-06-12 14:50 ` Rich Freeman
2020-06-12 15:05 ` Jack
2020-06-12 15:14 ` Michael
2020-06-12 13:45 ` Rich Freeman
2020-06-11 19:07 ` n952162
2020-06-13 19:42 ` Andreas K. Hüttel
2020-06-13 22:05 ` n952162
2020-06-14 8:23 ` n952162
2020-06-14 20:07 ` n952162
2020-06-14 22:06 ` Neil Bothwick
2020-06-15 11:26 ` n952162
2020-06-15 14:20 ` J. Roeleveld
2020-06-15 14:36 ` n952162
2020-06-15 15:49 ` [gentoo-user] " Grant Edwards
2020-06-15 16:25 ` J. Roeleveld
2020-06-15 19:49 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2027654.irdbgypaU6@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox