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 795161381F3 for ; Thu, 8 Aug 2013 16:13:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 410AFE0AB3; Thu, 8 Aug 2013 16:13:14 +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 6EC04E0A7E for ; Thu, 8 Aug 2013 16:13:13 +0000 (UTC) Received: from [192.168.1.35] (180.Red-2-137-23.dynamicIP.rima-tde.net [2.137.23.180]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id BB6F233EB2F for ; Thu, 8 Aug 2013 16:13:11 +0000 (UTC) Message-ID: <1375978388.6512.11.camel@localhost> Subject: Re: [gentoo-dev] Gnome Stabilization 3.6 or 3.8 From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Date: Thu, 08 Aug 2013 18:13:08 +0200 In-Reply-To: References: <5202416C.5@gentoo.org> <1375881254.7753.41.camel@rook> <5202DD20.8050906@gentoo.org> <5203A880.1050306@gentoo.org> <5203B190.80306@gentoo.org> <5203B660.30807@gmail.com> <5203BC0A.4030205@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: 17947ed0-ed2f-461d-8891-f34296835da0 X-Archives-Hash: 27466a70269cc09e91bca4cf2a23620e El jue, 08-08-2013 a las 12:02 -0400, Rich Freeman escribió: > On Thu, Aug 8, 2013 at 11:40 AM, Ian Stakenvicius wrote: > > It may be pertinent for this reason (a "smoother" upgrade path) and > > this reason alone, to stabilize gnome-3.6 first -- just to get into > > gnome3 (and get gnome-2 removed) without having to also deal with the > > systemd migration at the same time. > > I'd defer to Pacho who seems to be giving thought to planning for the > upgrade path. > > My suggestion would be that it would make more sense to first switch > to systemd running the current gnome. Switching to systemd is really > the harder change here, and systemd works just fine with earlier > versions of gnome AFAIK. There are already migration guides for > systemd (though I haven't tried them recently - the last time I did I > got burned by the fact that dhcpcd doesn't run by default as it does > in openrc-oldnet (or whatever we're going to call it)). Migrating to > systemd on a system that doesn't run many services isn't actually that > hard. The biggest pain is hunting down unit files if you have a lot > of things that don't provide them, and doing all the config (anything > in /etc/conf.d basically needs a redo). > > Rich > > In my case, I updated from 2.32 to 3.7.9x and, some weeks ago, moved from openrc to systemd. I don't know how is systemd working with 2.32 then. My idea would be to suggest to do all at the same time -> once all is ready and Gnome 3.8 is stabilized, people will see a news item telling them that they need to update their systems (telling them how to skip blockers and such things) and pointing them to migrate to systemd after that (and finally reboot). Regarding the blockers, we are working about how to handle them in a better way currently (or, at least, explain people how to skip them). About migration to systemd, I have followed: http://wiki.gentoo.org/wiki/Systemd without any problems. Most of the problems comes from packages still not providing unit files in their stable versions (that tries to be covered in https://bugs.gentoo.org/show_bug.cgi?id=unit-in-stable before Gnome 3.8 hits stable, that way people will have a better working systemd setup)