From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 591981381F3 for ; Thu, 17 Oct 2013 19:51:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 44616E0AFC; Thu, 17 Oct 2013 19:51:31 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 81C7EE0AD9 for ; Thu, 17 Oct 2013 19:51:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 68D5433F017 for ; Thu, 17 Oct 2013 19:51:29 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -1.514 X-Spam-Level: X-Spam-Status: No, score=-1.514 tagged_above=-999 required=5.5 tests=[AWL=-0.971, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.541, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no Received: from smtp.gentoo.org ([IPv6:::ffff:127.0.0.1]) by localhost (smtp.gentoo.org [IPv6:::ffff:127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ULbq0HuAgNKo for ; Thu, 17 Oct 2013 19:51:23 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id B61FF33F024 for ; Thu, 17 Oct 2013 19:51:19 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VWtbI-0001VN-OR for gentoo-desktop@gentoo.org; Thu, 17 Oct 2013 21:51:16 +0200 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 17 Oct 2013 21:51:16 +0200 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 17 Oct 2013 21:51:16 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-desktop@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-desktop] Re: Problem Emerging Gnome3 on Fresh Install Date: Thu, 17 Oct 2013 19:50:57 +0000 (UTC) Message-ID: References: <20131017144457.GA2600@ghostwheel> <1382028261.12495.35226749.21F38387@webmail.messagingengine.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-desktop@lists.gentoo.org Reply-to: gentoo-desktop@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT 6e6fd84 /usr/src/portage/src/egit-src/pan2) X-Archives-Salt: 3483f850-71be-4c35-9a32-b6f14c00ea66 X-Archives-Hash: 314f3d8cfde912be3526811ca4c8012e 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