[oe] generate a named kernel in ${DEPLOY_DIR_IMAGE}

[Andrea Adami]

On Wed, Sep 29, 2010 at 3:10 PM, Frans Meulenbroeks
<fransmeulenbroeks at gmail.com> wrote:
> 2010/9/29 Andrea Adami <andrea.adami at gmail.com>:
>> On Wed, Sep 29, 2010 at 8:54 AM, Frans Meulenbroeks
>> <fransmeulenbroeks at gmail.com> wrote:
>>> 2010/9/29 Andrea Adami <andrea.adami at gmail.com>:
>
>>> I would have expected you had to add something like:
>>> FILESPATHPKG_append = ":linux-${PV}"
>>> I had to add this to get access to the linux patches.
>>
>> No need to extend FILESPATHPKG being we keep the patches in the
>> kernel-specific dirs: e.g. /linux-2.6.34 and /linux-kexecboot-2.6.34
>
> Ah ok, I understand. As I am building different versions of the
> standard kernel, I am using those patches
> I assumed kexecboot also used the same patches as the kernel does.
> I expected these would apply to the kexecboot kernel with the same name.
>
Sure, the patches are the same and FILESPATHPKG could avoid patch
duplication: only defconfig differ.
At first I moved the kernels here, as second step I'll lead the
obsoleted to rest, finally I'll take care of this duplicated patches.

> The question was whether it would be better to explicitly say
>  S = "${WORKDIR}/linux-${PV}"
> in linux_${PN}.bb
> then S is always automatically ok for everyone who includes it.
>
> not a big change and not very important either.
>
> Frans

Well, or having it once in linux.inc. Recipes can override after
'require linux.inc' if needed.
Feel free to propose a patch, thx.

Regards

Andrea

>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>