Gentoo Archives: gentoo-catalyst

From: Marco Gigante <m.gigante@×××××××××.it>
To: gentoo-catalyst@l.g.o
Subject: Re: [gentoo-catalyst] genkernel version parsing problem
Date: Thu, 21 Apr 2016 06:34:08
Message-Id: 57187458.3020106@nextworks.it
In Reply to: Re: [gentoo-catalyst] genkernel version parsing problem by Leno Hou
1 On 21/04/2016 07:48, Leno Hou wrote:
2 > On Thu, Apr 21, 2016 at 1:42 PM, Mike Frysinger <vapier@g.o
3 > <mailto:vapier@g.o>> wrote:
4 >
5 > On 15 Apr 2016 09:54, Marco Gigante wrote:
6 > > I got a problem with catalyst and latest version of genkernel,
7 > installed
8 > > with genkernel-9999 ebuild.
9 > > genkernel --version returns v3.5.0.1 (with the 'v' prefix) and
10 > catalyst
11 > > fails to check the minimal required version.
12 >
13 > is this new to 3.5.0.1 ? or did it happen with 3.5.0.0 ? i don't
14 > think
15 > it was intentional, so we can always just change genkernel ...
16 >
17
18 I looked at genkernel before writing and GK_V is "3.5.0.1". Couldn't
19 quickly figure out where the 'v' comes from.
20
21 I just analysed the issue, and it is the genkernel-9999 ebuild which
22 modifies the GK_V into src_prepare(), by picking the git tag as version
23 number.
24 Not sure which is better, change genkernel or catalyst. I guess
25 protecting version check in catalyst will make it more reliable anyway.
26
27 -marco
28
29 > -mike
30 >
31 >
32 > Faced the problem only in v3.5.0.1. Not happen in v3.5.0.0
33 >
34 > leno@localhost~ $ genkernel --version
35 >
36 > v3.5.0.1
37 >
38 >
39 > -Leno Hou