| 1 |
On Thu, Apr 01, 2010 at 12:23:42PM +0100, Ciaran McCreesh wrote: |
| 2 |
> On Thu, 1 Apr 2010 03:59:54 -0700 |
| 3 |
> Brian Harring <ferringb@×××××.com> wrote: |
| 4 |
> > On Thu, Apr 01, 2010 at 12:42:10PM +0200, Gilles Dartiguelongue wrote: |
| 5 |
> > > > Basically, you want the PM to lie to the ebuild in some fashion. |
| 6 |
> > > > Since pkg_pretend is free form, it's effectively impossible to |
| 7 |
> > > > cover the scenarios it could check on- consider checking the |
| 8 |
> > > > kernel config/version, or checking the active jvm/python version. |
| 9 |
> > > |
| 10 |
> > > except the kernel will not change during the upgrade, |
| 11 |
> > |
| 12 |
> > Pardon, I wasn't clear- I was referring to kernel sources, not |
| 13 |
> > the running kernel. |
| 14 |
> |
| 15 |
> But if the kernel sources symlink is changed by installing new kernel |
| 16 |
> sources, there won't be a valid .config in the new directory anyway. |
| 17 |
|
| 18 |
Oddly enough, I actually have an ebuild that directly contradicts |
| 19 |
that- used for managing my sources w/in kvms. |
| 20 |
|
| 21 |
> Thus, pkg_pretend doesn't introduce any new breakage. |
| 22 |
|
| 23 |
Regardless of my own usage, ironically you just inadvertantly pointed |
| 24 |
out a whole class of false negatives pkg_pretend has. |
| 25 |
|
| 26 |
Specifically, |
| 27 |
|
| 28 |
1) starting w/ a configured kernel at /usr/src/linux |
| 29 |
2) merging a version of aufs2 requiring new kernel sources |
| 30 |
3) emerge runs pkg_pretend. aufs2 does it's checks w/in pkg_pretend, |
| 31 |
sees the old configured kernel and thinks things are fine |
| 32 |
4) new kernel sources get merged. /usr/src/linux is no lnger a |
| 33 |
configured kernel. |
| 34 |
5) aufs2 blows up during its build due to an unconfigured |
| 35 |
kernel. |
| 36 |
|
| 37 |
Since I'm in the mood for a Scooby Doo quote, "wraut-wroh". |
| 38 |
|
| 39 |
~harring |
Archives