| 1 |
I was attempting to make a local ebuild of the 2.6.2-rc1-mm1 kernel |
| 2 |
sources. I used mm-sources-2.6.1-r5.ebuild as a template. Since this |
| 3 |
is an -rc kernel, the ${OKV} variable is set to 2.6.1. I set |
| 4 |
UNIPATCH_LIST to: |
| 5 |
|
| 6 |
UNIPATCH_LIST="${DISTDIR}/patch-${TKV}.bz2 ${DISTDIR}/${KV}.bz2" |
| 7 |
|
| 8 |
|
| 9 |
That expands to |
| 10 |
|
| 11 |
"/.../distfiles/patch-2.6.1-rc1.bz2 /.../distfiles/2.6.2-rc1-mm1.bz2" |
| 12 |
|
| 13 |
I verified this by putting an echo command in the kernel-2.eclass |
| 14 |
file. What happens is that the "2.6.2-rc1-mm1" patch is the first |
| 15 |
patch attempted during the build. This fails of course because |
| 16 |
"patch-2.6.1-rc1" needs to be applied first. |
| 17 |
|
| 18 |
The problem is when the patches are looked for in the ${KPATCH_DIR}. |
| 19 |
|
| 20 |
---begin code--- |
| 21 |
# and now, finally, we patch it :) |
| 22 |
for x in ${KPATCH_DIR} |
| 23 |
do |
| 24 |
for i in $(find ${x} -maxdepth 1 -iname "*.patch" -or -iname "*.diff" | sort -u) |
| 25 |
do |
| 26 |
. |
| 27 |
. |
| 28 |
. |
| 29 |
---end code--- |
| 30 |
|
| 31 |
Is there a way to enforce the order that the patches are applied? |
| 32 |
|
| 33 |
Thanks. |
| 34 |
|
| 35 |
-- |
| 36 |
Glenn Johnson |
| 37 |
glennpj@×××××××.net |
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-dev@g.o mailing list |
Archives