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 346201381F3 for ; Sun, 14 Apr 2013 09:29:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 81088E09BE; Sun, 14 Apr 2013 09:29:52 +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 9A90BE09BA for ; Sun, 14 Apr 2013 09:29:51 +0000 (UTC) Received: from [192.168.1.33] (117.Red-88-11-52.dynamicIP.rima-tde.net [88.11.52.117]) (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 2AA4B33DD26 for ; Sun, 14 Apr 2013 09:29:49 +0000 (UTC) Message-ID: <1365931786.6940.4.camel@localhost> Subject: Re: [gentoo-dev] Re: [PATCHES] kernel-2.eclass: Various changes requested by users. + [STABLEREQ?] sys-kernel/gentoo-sources-3.8.7: Any objections against stabilizing? From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Date: Sun, 14 Apr 2013 11:29:46 +0200 In-Reply-To: <20130414085539.7501576a@TOMWIJ-GENTOO> References: <20130412234105.407563f4@TOMWIJ-GENTOO> <20130413230905.76013d0e@caribou.gateway.2wire.net> <20130414085539.7501576a@TOMWIJ-GENTOO> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.0 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: af821916-e0d9-447d-a2f6-25a920009626 X-Archives-Hash: 8f347d494217083dfb86e7c8ef083a10 El dom, 14-04-2013 a las 08:55 +0200, Tom Wijsman escribió: > On Sat, 13 Apr 2013 23:09:05 -0600 > Ryan Hill wrote: > > > > > - Make use of readme.gentoo.eclass to make the user aware of the > > > Gentoo Linux Kernel Upgrade Guide only the first time he emerges > > > the package. Fixes bug #457598. > > > > Call me crazy, but upgrade guides seem like something you might want > > to tell the user about during an upgrade. > > True, I was wondering if there is a way to show it on their first > upgrade instead; most users would indeed not be able or forget to > bookmark this during their handbook install. > > Therefore, I won't commit this patch. > > I wonder if Pacho can adapt the eclass to allow us to do this on the > first upgrade, If I were able to know how to detect only "first update" that would be nice, but I don't have any idea to achieve that for now :( > I have explicitly put him in CC so he can consider that. > Perhaps he can also explain why he wanted to see this change happen. > Because I see no gain on getting the link to the same upgrade guide on every update: some times after you upgrade the kernel, I think we all are able to remember how to upgrade kernels . Maybe one option could even add a link pointing to the kernel upgrade guide from Handbook in its kernel section. That way, people could see they will need to follow some steps to upgrade kernels when an update for them arrives and, then, visit it in next kernel update (but, once they update the kernel, they won't need to revisit it on every update as they will likely remember how to do that) > I thought the goal of this eclass is to get rid of repeating messages > that are not that important from the elog. After you have installed the > kernel twice you should be able to do it a third time. People that > really still need the link have it either bookmarked or can look into > that file, Yes, that was my point