Gentoo Archives: gentoo-dev

From: Pacho Ramos <pacho@g.o>
To: gentoo-dev@l.g.o
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?
Date: Sun, 14 Apr 2013 09:29:56
Message-Id: 1365931786.6940.4.camel@localhost
In Reply to: 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? by Tom Wijsman
1 El dom, 14-04-2013 a las 08:55 +0200, Tom Wijsman escribió:
2 > On Sat, 13 Apr 2013 23:09:05 -0600
3 > Ryan Hill <dirtyepic@g.o> wrote:
4 > >
5 > > > - Make use of readme.gentoo.eclass to make the user aware of the
6 > > > Gentoo Linux Kernel Upgrade Guide only the first time he emerges
7 > > > the package. Fixes bug #457598.
8 > >
9 > > Call me crazy, but upgrade guides seem like something you might want
10 > > to tell the user about during an upgrade.
11 >
12 > True, I was wondering if there is a way to show it on their first
13 > upgrade instead; most users would indeed not be able or forget to
14 > bookmark this during their handbook install.
15 >
16 > Therefore, I won't commit this patch.
17 >
18 > I wonder if Pacho can adapt the eclass to allow us to do this on the
19 > first upgrade,
20
21 If I were able to know how to detect only "first update" that would be
22 nice, but I don't have any idea to achieve that for now :(
23
24 > I have explicitly put him in CC so he can consider that.
25 > Perhaps he can also explain why he wanted to see this change happen.
26 >
27
28 Because I see no gain on getting the link to the same upgrade guide on
29 every update: some times after you upgrade the kernel, I think we all
30 are able to remember how to upgrade kernels . Maybe one option could
31 even add a link pointing to the kernel upgrade guide from Handbook in
32 its kernel section. That way, people could see they will need to follow
33 some steps to upgrade kernels when an update for them arrives and, then,
34 visit it in next kernel update (but, once they update the kernel, they
35 won't need to revisit it on every update as they will likely remember
36 how to do that)
37
38
39
40 > I thought the goal of this eclass is to get rid of repeating messages
41 > that are not that important from the elog. After you have installed the
42 > kernel twice you should be able to do it a third time. People that
43 > really still need the link have it either bookmarked or can look into
44 > that file,
45
46 Yes, that was my point