From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-desktop@lists.gentoo.org
Subject: [gentoo-desktop] Re: Problem Emerging Gnome3 on Fresh Install
Date: Thu, 17 Oct 2013 19:50:57 +0000 (UTC) [thread overview]
Message-ID: <pan$c0d13$d2e4ed57$a4e9d00b$711b4f18@cox.net> (raw)
In-Reply-To: 1382028261.12495.35226749.21F38387@webmail.messagingengine.com
marduk posted on Thu, 17 Oct 2013 12:44:21 -0400 as excerpted:
> Doing everything at once (IMO) is just a recipe for headaches. The best
> thing is to do smaller steps, verify, then move to the next step. Sure
> you can do everything in one step, but when there is a problem it will
> be more difficult to figure out which change created which problem (was
> it switching to testing? switching to systemd? etc.).
FWIW as a kde user not a gnomie, but with a decade on gentoo early next
year, I'll heartily endorse that recommendation! All sorts of stuff is
possible on gentoo and it's more flexible than most binary distro users
could begin to imagine, but by the same token major changes can and do
occasionally get quite complex, and taking it a step at a time and
bringing the system to a consistent state (or as consistent as possible,
sometimes you break the consistent steps down into smaller steps too, and
only make sure the individual area you're working on is consistent for
that sub-step) at each step is /the/ way to success.
The same general policy applies once you're all current, if you then
slack off for a year and don't do updates, then try to get current
again. I do updates on my main machine generally weekly if not more
often, but I sometimes go a year or more between netbook updates[1],
which means there's almost certain to be blockers when I try to update
everything at once, but by breaking the big update into smaller
intermediate steps and just updating what I can at each step, I resolve
them one by one until there's no blockers remaining and I'm fully updated
once again.
---
[1] I deliberately don't keep anything personal but the user passwords
themselves on the netbook, and contrary to what the name netbook implies,
I don't actually have wifi setup or do much networking other than behind
the local firewall with it, so otherwise vital security updates aren't a
big deal as exposure is very limited.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-10-17 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 14:44 [gentoo-desktop] Problem Emerging Gnome3 on Fresh Install Tyrin Price
2013-10-17 16:44 ` marduk
2013-10-17 19:50 ` Duncan [this message]
2013-10-18 1:48 ` Tyrin Price
2013-10-19 2:27 ` Tyrin Price
2013-10-19 2:39 ` Tyrin Price
2013-10-19 13:39 ` marduk
2013-10-19 14:13 ` Tyrin Price
2013-10-19 14:43 ` marduk
2013-10-19 23:17 ` Tyrin Price
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='pan$c0d13$d2e4ed57$a4e9d00b$711b4f18@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-desktop@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