From: Tom Wijsman <TomWij@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] Which Kernel?
Date: Tue, 26 Feb 2013 19:13:18 +0100 [thread overview]
Message-ID: <20130226191318.2fec648c@gentoo.org> (raw)
In-Reply-To: <alpine.LNX.2.10.1302261830130.9535@chalice.crownest.nephros.org>
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]
On Tue, 26 Feb 2013 18:37:16 +0100 (CET)
"Peter Gantner \(nephros\)" <gentoo@nephros.org> wrote:
> Actually I have always wondered why the kernels are SLOTted by
> complete version and not just series. I imagine many peoples lives
> would be easier if they could just unmask xxx-sources:3.4 and
> therefore always get the current "upstream-stable" version of their
> preferred kernel.
>
> But then there are probably good reasons for the way it is done. (Or,
> maybe, it is a holdover from 2.6.xx days where the two dots made more
> sense for SLOTs?)
As an easy way to keep a single kernel version from being unmerged by
a kernel upgrade in Portage, I think.
emerge gentoo-sources:3.7.9
If you then also have a plain gentoo-sources and a mask on anything
non-3.4 it becomes simple to pick which version you want to stay on as
well as to have the latest sources always available for when you decide
to spent some time upgrading to the latest version on your branch.
# I want the 3.4 branch! I compile and install 3.4.32.
echo ">=sys-kernel/gentoo-sources-3.4" >> /etc/portage/package.mask
emerge gentoo-sources
emerge --noreplace gentoo-sources:3.4.32
# After a world update I decide I want to upgrade it, I do 3.4.33.
emerge -uDN @world
emerge --noreplace gentoo-sources:3.4.33
# Ah, 3.4.33 works fine, I can get rid of the old version now.
emerge -C gentoo-sources:3.4.32
rm /usr/src/*3.4.32*
If you were to make the SLOTS branch based you would get rid of the
mask line in above example; but its side effect is that it would also
get rid of the easy SLOT syntax which will require you to specify
the full ATOM specification whenever you want to keep a version
around, or unmerge another. This is not worth the change...
Of course, this is just one approach to it; feel free to share a
different work flow if your approach differs from the above one.
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-02-26 18:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 6:05 [gentoo-kernel] Which Kernel? Gino!
2013-02-25 11:51 ` Tom Wijsman
2013-02-25 17:35 ` Peter Gantner (nephros)
2013-02-26 10:28 ` Marc Schiffbauer
2013-02-26 17:37 ` Peter Gantner (nephros)
2013-02-26 18:13 ` Tom Wijsman [this message]
2013-02-27 12:07 ` Marc Schiffbauer
2013-02-27 12:49 ` Tom Wijsman
2013-02-27 15:39 ` Marc Schiffbauer
2013-02-27 16:24 ` Tom Wijsman
2013-02-28 13:26 ` Marc Schiffbauer
2013-02-25 17:43 ` [gentoo-kernel] " Gino!
2013-02-25 14:26 ` [gentoo-kernel] " Greg KH
2013-02-25 17:27 ` [gentoo-kernel] " Gino!
2013-02-25 18:00 ` Tom Wijsman
2013-02-26 7:01 ` Thierry
2013-02-26 14:27 ` Greg KH
2013-02-26 17:45 ` Tom Wijsman
2013-02-26 19:10 ` Gino!
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=20130226191318.2fec648c@gentoo.org \
--to=tomwij@gentoo.org \
--cc=gentoo-kernel@lists.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