From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: kernel type naming and package version conflicts
Date: Tue, 14 Dec 2010 13:43:52 -0800 [thread overview]
Message-ID: <4D07E518.7020903@linux.intel.com> (raw)
In-Reply-To: <AANLkTi=S66To=45rywH50VJS2pC0TNXkOYtJC73xpLsR@mail.gmail.com>
On 12/14/2010 01:20 PM, Bruce Ashfield wrote:
> On Tue, Dec 14, 2010 at 3:52 PM, Darren Hart<dvhart@linux.intel.com> wrote:
>> I believe I've identified why my preempt_rt kernel recipes are failing to
>> build. The do_package_write_ipk is complaining about invalid characters in
>> the file name - specifically:
>>
>> kernel-2.6.34.7-rt-yocto-preempt_rt
>> *** Error: Package name contains illegal characters, (other than
>> [a-z0-9.+-])
>>
>> Note the "_" in preempt_rt.
>>
>> This name appears to be generated in part from the following assignment:
>>
>> LINUX_KERNEL_TYPE = "preempt_rt"
>> LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
>>
>> Changing this to the following allows the build to succeed without error
>> (replacing _ with -).
>> LINUX_VERSION_EXTENSION ?= "-yocto-preempt-rt"
>>
>> As I see it we have two options, we can rewrite linux-yocto kernel branches
>> for use in bitbake package names (replacing _ with -), or we can forbid the
>> use of _ in the linux-yocto git branches. Rather than clutter up the recipes
>> with string manipulators, I would prefer the latter option.
>
> Ah yes. The _ in preempt_rt pre-dates bitbake, but I'm not particularly
> attached to it.
>
> As for forbidding, I'll have to add sanity checks, since the branch names
> are board customizable, and I know of plenty that will use _'s.
>
>>
>> Bruce, Tom, do you have an opinion?
>
> I'll fix preempt_rt to be preempt-rt, and add sanity checks, but won't
> go for full replacement.
>
> How does that sound ?
Sounds sound ;-)
Thanks,
--
Darren Hart
Yocto Linux Kernel
prev parent reply other threads:[~2010-12-14 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 20:52 kernel type naming and package version conflicts Darren Hart
2010-12-14 21:20 ` Bruce Ashfield
2010-12-14 21:43 ` Darren Hart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D07E518.7020903@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@gmail.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.