From: Tom Wijsman <TomWij@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: pacho@gentoo.org
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 08:55:39 +0200 [thread overview]
Message-ID: <20130414085539.7501576a@TOMWIJ-GENTOO> (raw)
In-Reply-To: <20130413230905.76013d0e@caribou.gateway.2wire.net>
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
On Sat, 13 Apr 2013 23:09:05 -0600
Ryan Hill <dirtyepic@gentoo.org> 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, 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.
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, another concern here is that nothing mentions its existence.
The user would have to spot it in the list of installed files, strange.
If I misunderstood the goal of this eclass, sorry, it's not documented.
I thought people were against these kind of repeating messages in elog.
- http://devmanual.gentoo.org/eclass-reference/readme.gentoo.eclass
- Bug in discussion: https://bugs.gentoo.org/show_bug.cgi?id=457598
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-04-14 6:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 21:41 [gentoo-dev] [PATCHES] kernel-2.eclass: Various changes requested by users. + [STABLEREQ?] sys-kernel/gentoo-sources-3.8.7: Any objections against stabilizing? Tom Wijsman
2013-04-13 7:03 ` Fabio Erculiani
2013-04-13 9:07 ` Tom Wijsman
2013-04-14 5:09 ` [gentoo-dev] " Ryan Hill
2013-04-14 6:55 ` Tom Wijsman [this message]
2013-04-14 8:24 ` Ryan Hill
2013-04-14 8:23 ` Andreas K. Huettel
2013-04-14 10:08 ` Ryan Hill
2013-04-14 10:06 ` Pacho Ramos
2013-04-14 10:52 ` Tom Wijsman
2013-04-14 15:02 ` Alan McKinnon
2013-04-14 17:15 ` Andreas K. Huettel
2013-04-14 17:21 ` Pacho Ramos
2013-04-14 9:31 ` Pacho Ramos
2013-04-14 9:29 ` Pacho Ramos
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=20130414085539.7501576a@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pacho@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