[yocto] PN is uppercase

[Khem Raj]

On 5/21/19 12:50 AM, Ralf Spiwoks wrote:
> Hi Ross,
> 
> Thanks for your email. I am realising that I have not replied to your
> email earlier. Sorry. I guess it was partly because your answer put
> me slightly off. On the one hand, I thought that as a general approach,
> Linux was case sensitive, unlike its big rival Windows, and I was not
> aware  of package managers which would explicitly forbid uppercase
> package names. I find the approach of allowing only lowercase package
> names quite limiting, and frankly a drawback for using Yocto
> 
> On the other hand I have a few tens of packages to maintain, which
> have uppercase letters in the package names and which did work with
> Yocto in previous versions. So, because of a new convention we would
> have to rework some of the packages or ignore the warning messages.
> And until we find the effort for reworking those package recipes we
> will stay with the latter option.

The package name rules are not new, they have been with OE/YP forever
so it should have failed always. Similar to debian see

https://www.debian.org/doc/debian-policy/ch-controlfields.html#list-of-fields

> 
> Thanks for your patience and your explanations. Cheers,
> 
> Ralf.
> 
> On 4/2/19 1:54 PM, Burton, Ross wrote:
>> On Tue, 2 Apr 2019 at 12:36, Ralf Spiwoks <spiwoks at cern.ch> wrote:
>>> TWO questions:
>>>
>>> 1) Are those two issues related?
>>
>> Probably not, unless you're trying to use a mixed-case override.
>>
>>> 2) What is the logic behind allowing only lower case package names? 
>>> This is to me
>>>      a serious restriction on the use of Yocto.
>>
>> Two reasons: some package managers forbid packages with uppercase
>> names; and for performance reasons overrides are lowercase and as
>> package names are often embedded in overrides this implies that
>> package names need to be lowercase.
>>
>> What's the problem with using lowercase names?
>>
>> Ross
>>