| 1 |
On Wed, 2008-02-13 at 22:11 -0500, Mike Frysinger wrote: |
| 2 |
> On Wednesday 13 February 2008, lurker wrote: |
| 3 |
> > Currently catalyst (2.0.5, 2.0.6pre4) doesn't seem to change what uname |
| 4 |
> > outputs. uname -r, for example, prints the version of the kernel running |
| 5 |
> > catalyst, not the kernel that's in the stage. Of course, that's how it |
| 6 |
> > is, but isn't it possible to hack that somehow? It's a bit tedioius to |
| 7 |
> > patch everything that depends on uname (e.g. the raling-rt61 ebuild). |
| 8 |
> > Can the "uname string" be set by some envirnoment variable in an env |
| 9 |
> > script specified in the spec file? |
| 10 |
> |
| 11 |
> stages dont have kernels |
| 12 |
|
| 13 |
Indeed. As Andrew has said and Mike as alluded to, not a single |
| 14 |
catalyst target has a kernel compiled prior to stage4/livecd-stage2, so |
| 15 |
there's no reason for this. Any ebuild that uses uname for *anything* |
| 16 |
is broken and a bug should be filed to have the package fixed. |
| 17 |
|
| 18 |
-- |
| 19 |
Chris Gianelloni |
| 20 |
Release Engineering Strategic Lead |
| 21 |
Games Developer |
Archives