[yocto] PN is uppercase

[Burton, Ross]

The check was added in August 2017 and appeared first in Rocko, so
it's possible that you stuck with an earlier release until recently.

Ross

On Fri, 24 May 2019 at 15:26, Ralf Spiwoks <spiwoks at cern.ch> wrote:
>
> Hi guys,
>
> The warnings were definitely not on when I started using Yocto more than two years ago.
> I have not been using debian packages, and didn't notice. I thought I was still not
> using debian and that's why I am surprised about those warnings. But as I wrote, if I
> ignore the warnings, nothing bad happens ...
>
> And Tim, thank you for writing "Debian" and "OpenEmbedded" in that way ... it reassured
> me ;-)
>
> Have a good weekend. Cheers,
>
> Ralf.
>
> On 5/24/19 6:23 AM, Tim Orling wrote:
> >
> >
> > On Thu, May 23, 2019 at 4:55 PM Khem Raj <raj.khem at gmail.com <mailto:raj.khem at gmail.com>> wrote:
> >
> >
> >
> >     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
> >
> >
> > We had to pick a convention. Debian is well documented, conservative and well thought out. My first contributions to OpenEmbedded many years ago
> > didn’t follow Debian naming, were rejected on V1 and I embarked on a new learning curve. I’ve embraced it and never looked back.
> >
> >
> >      >
> >      > 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 <mailto: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
> >      >>
> >     --
> >     _______________________________________________
> >     yocto mailing list
> >     yocto at yoctoproject.org <mailto:yocto at yoctoproject.org>
> >     https://lists.yoctoproject.org/listinfo/yocto
> >