| 1 |
On Thu, 1 Apr 2010 03:59:54 -0700 |
| 2 |
Brian Harring <ferringb@×××××.com> wrote: |
| 3 |
> On Thu, Apr 01, 2010 at 12:42:10PM +0200, Gilles Dartiguelongue wrote: |
| 4 |
> > > Basically, you want the PM to lie to the ebuild in some fashion. |
| 5 |
> > > Since pkg_pretend is free form, it's effectively impossible to |
| 6 |
> > > cover the scenarios it could check on- consider checking the |
| 7 |
> > > kernel config/version, or checking the active jvm/python version. |
| 8 |
> > |
| 9 |
> > except the kernel will not change during the upgrade, |
| 10 |
> |
| 11 |
> Pardon, I wasn't clear- I was referring to kernel sources, not |
| 12 |
> the running kernel. |
| 13 |
|
| 14 |
But if the kernel sources symlink is changed by installing new kernel |
| 15 |
sources, there won't be a valid .config in the new directory anyway. |
| 16 |
Thus, pkg_pretend doesn't introduce any new breakage. |
| 17 |
|
| 18 |
-- |
| 19 |
Ciaran McCreesh |
Archives