[OE-core] [PATCH 4/4] linux-firmware: Break out some additional firmware

Phil Blundell pb at pbcl.net
Tue Mar 22 23:09:28 UTC 2016


On Tue, 2016-03-22 at 22:37 +0000, Burton, Ross wrote:
> 
> 
> On 22 March 2016 at 21:56, Saul Wold <sgw at linux.intel.com> wrote:
> 
>         > | linux-firmware-iwlwifi-7265D
>         > | *** Error: Package name  contains illegal characters,
>         (other than
>         > [a-z0-9.+-])
>         >
>         Gah, no CAPS?  Sorry I did not do the full package specturm
>         tests.
>         
> 
> 
> Yeah...  tempting to file a bug against opkg!


That restriction comes from opkg's Debian roots.  See:

https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Source

"Package names (both source and binary, see Package, Section 5.6.7) must
consist only of lower case letters (a-z), digits (0-9), plus (+) and
minus (-) signs, and periods (.). They must be at least two characters
long and must start with an alphanumeric character."

So, I don't think that filing against opkg is likely to produce any
useful result because the opkg maintainer will probably argue
(correctly) that it is operating as designed.  On the other hand,
there's no reason that package_ipk couldn't be taught how to massage
otherwise-illegal package names into a format that opkg-build will
accept, and I think there might even be some precedent for that sort of
thing in OE already.

But on the third hand, we've lived with this restriction for more than a
decade, we don't seem to have exhausted the namespace of lower-case
letters, and I haven't seen any other particularly compelling reason for
wanting to use capitals in package names.  So personally I would leave
it alone.

p.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160322/bece311a/attachment-0002.html>


More information about the Openembedded-core mailing list