public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: rdalek1967@gmail.com
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Official way to do rolling update (Was: Re: Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec)
Date: Mon, 4 Nov 2013 13:28:34 +0100	[thread overview]
Message-ID: <20131104132834.27fe7dfb@TOMWIJ-GENTOO> (raw)
In-Reply-To: <52778DDC.7080407@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2308 bytes --]

On Mon, 04 Nov 2013 06:06:52 -0600
Dale <rdalek1967@gmail.com> wrote:

> But after a person has used Gentoo a while, they figure out what
> process leads to the most stable update process.

Do they? What do you consider a stable update process?

I come across users on a daily basis which

 - haven't upgraded their system lately because they're not good at it;
 - get into unclear slot conflicts locking them out of updates;
 - some build failure disallows their dependency graph from completing;
 - managed to finally update, but don't know about depclean;
 - managed to finally depclean, but don't know about eclean.

It involves a lot of prior knowledge, manual checking and what in order
to be able to update the system; I wouldn't label this "stable", but
rather "dependent on the person updating it" and to some extent even
"dependent on whether the person memorized all the docs and/or gets
helped or get it told in the support channels".

There are some improvements possible in these situations; I'm planning
to discuss some ideas and write some patches where possible, and I
hope other people jump on the bandwagon to help improve user experience.

That doesn't mean I consider it bad or that we need to go hand holding.

> The only way to get a more stable system is to do a emerge -e world
> and update that way.  At least that has been my experience so far.

I have never needed this; I wonder whether there exists an example case
for this, I only see this used when someone changes compiler / flags
and wants to ensure the whole system turns into rice. *

> If Zac adds some other nifty feature, then I may add to the above as
> needed. For the past few years, that has resulted in as stable a
> system as I can get.  I do from time to time run emerge -e world just
> for giggles when I have something acting odd and can't put my finger
> on the issue. Sometimes, that fixes it, sometimes not.
> 
> Again, most of this comes from experience.  The handbook explains it
> then the user figures it out from there.

 * http://funroll-loops.info/

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-11-04 12:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  4:15 Official way to do rolling update (Was: Re: [gentoo-dev] Releng breakage with respect to move from dev-python/python-exec to dev-lang/python-exec) yac
2013-11-04  8:50 ` Daniel Campbell
2013-11-04  9:51   ` [gentoo-dev] Re: Official way to do rolling update (Was: " Duncan
2013-11-04 10:26     ` yac
2013-11-04 12:06       ` Dale
2013-11-04 12:28         ` Tom Wijsman [this message]
2013-11-04 15:50           ` Rich Freeman
2013-11-04 20:02           ` Dale
2013-11-04 20:27             ` Tom Wijsman
2013-11-04 21:47               ` Dale
2013-11-04 23:28           ` Alan McKinnon
2013-11-04 12:12       ` Tom Wijsman
2013-11-04 22:28       ` Duncan
2013-11-04 11:17     ` Martin Vaeth
2013-11-04 21:46       ` Duncan
2013-11-05  1:23         ` Michael Orlitzky
2013-11-05  7:51           ` Duncan
2013-11-05 16:21         ` Daniel Campbell
2013-11-04 21:53     ` Peter Stuge
2013-11-04 11:07 ` Official way to do rolling update (Was: Re: [gentoo-dev] " Tom Wijsman

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=20131104132834.27fe7dfb@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=rdalek1967@gmail.com \
    /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