1 |
On Thu, 1 Apr 2010 04:38:36 -0700 |
2 |
Brian Harring <ferringb@×××××.com> wrote: |
3 |
> > But if the kernel sources symlink is changed by installing new |
4 |
> > kernel sources, there won't be a valid .config in the new directory |
5 |
> > anyway. |
6 |
> |
7 |
> Oddly enough, I actually have an ebuild that directly contradicts |
8 |
> that- used for managing my sources w/in kvms. |
9 |
|
10 |
Your own personal ebuilds are an exception that don't apply to |
11 |
everyone else. For ebuilds using kernel-2.eclass with USE=symlink, a |
12 |
missing .config is exactly what happens. |
13 |
|
14 |
> > Thus, pkg_pretend doesn't introduce any new breakage. |
15 |
> |
16 |
> Regardless of my own usage, ironically you just inadvertantly pointed |
17 |
> out a whole class of false negatives pkg_pretend has. |
18 |
> |
19 |
> Specifically, |
20 |
> |
21 |
> 1) starting w/ a configured kernel at /usr/src/linux |
22 |
> 2) merging a version of aufs2 requiring new kernel sources |
23 |
> 3) emerge runs pkg_pretend. aufs2 does it's checks w/in pkg_pretend, |
24 |
> sees the old configured kernel and thinks things are fine |
25 |
> 4) new kernel sources get merged. /usr/src/linux is no lnger a |
26 |
> configured kernel. |
27 |
> 5) aufs2 blows up during its build due to an unconfigured |
28 |
> kernel. |
29 |
> |
30 |
> Since I'm in the mood for a Scooby Doo quote, "wraut-wroh". |
31 |
|
32 |
This isn't a breakage that's introduced by pkg_pretend. It's a breakage |
33 |
that's already there. |
34 |
|
35 |
-- |
36 |
Ciaran McCreesh |