Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/4] linux-firmware: Break out some additional firmware
Date: Tue, 22 Mar 2016 23:09:28 +0000	[thread overview]
Message-ID: <1458688168.2038.41.camel@pbcl.net> (raw)
In-Reply-To: <CAJTo0LYKCiNA73zWkvXCHSz8-sWKQ4oAbQnqkyCZubf4BJ-xJA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1623 bytes --]

On Tue, 2016-03-22 at 22:37 +0000, Burton, Ross wrote:
> 
> 
> On 22 March 2016 at 21:56, Saul Wold <sgw@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.


[-- Attachment #2: Type: text/html, Size: 2357 bytes --]

      parent reply	other threads:[~2016-03-22 23:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 18:13 [PATCH 0/4] linux-firmware update and cleanup Saul Wold
2016-03-22 18:13 ` [PATCH 1/4] linux-firmware: Update to latest HEAD Saul Wold
2016-03-22 18:13 ` [PATCH 2/4] linux-firmware: Collapse iwlwifi firmware blobs for 7260 and 7265 Saul Wold
2016-03-22 18:13 ` [PATCH 3/4] linux-firmware: Clean-up and sync license data Saul Wold
2016-03-22 18:13 ` [PATCH 4/4] linux-firmware: Break out some additional firmware Saul Wold
2016-03-22 21:07   ` Otavio Salvador
2016-03-22 21:58     ` Saul Wold
2016-03-22 21:27   ` Burton, Ross
2016-03-22 21:56     ` Saul Wold
2016-03-22 22:37       ` Burton, Ross
2016-03-22 22:51         ` Paul Eggleton
2016-03-22 23:09         ` Phil Blundell [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=1458688168.2038.41.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox