11592 2017-05-30 10:24:10 +0000 Add QA check for uppercase recipe names 2017-09-15 01:56:42 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.3 x86 Multiple RESOLVED FIXED Medium enhancement 2.4 M3 1 bluelightning ee.peng.yeoh costamagnagianfranco dl9pf meta.mr.watcher meta.watcher sgw zuloch --- --- Yes (doc changes required) oldest_to_newest 73563 0 bluelightning 2017-05-30 10:24:10 +0000 Since we disabled uppercase characters in overrides a few releases ago, uppercase characters in recipe names (and for that matter, distro and machine names) cannot be supported due to their reliance upon overrides including the name. We should have a QA check and produce an error when an uppercase character is used in PN instead of leaving the user to figure it out from weird behaviour that will otherwise be the result. 75107 1 zuloch 2017-07-18 13:23:24 +0000 IMHO this bug should have a higher priority, simply because: - there is no place from where one could retrieve the information (talking about recipe's names in lowercase) - from my own experience using uppercase characters in recipe's names will lead to any kind of problems: I was in charge of porting an entire layer from yocto 1.8 to yocto 2.2.1 and it took a LOT of time (and lots of IRC sessions) to find out that all of my problems were caused by uppercase characters in recipe's names. 75851 2 ee.peng.yeoh 2017-08-15 07:29:59 +0000 As suggested by Paul, I am currently working on enhancement inside insane.bbclass to check for package name which is not lowercase and provide warning message. 76487 3 ee.peng.yeoh 2017-09-04 02:16:17 +0000 Patch to check recipe uppercase in insane.bbclass submitted to openembedded-core and it was accepted. 76688 4 costamagnagianfranco 2017-09-08 14:33:15 +0000 WARNING: build/../sources/meta-foo/recipes-extended/socketcan/Can_git.bb: QA Issue: PN: Can is upper case, this can result in unexpected behavior. [uppercase-pn]--:--:-- I can confirm the fix works flawlessly 76876 5 ee.peng.yeoh 2017-09-15 01:56:42 +0000 Pushed commit to mailing list for review: http://lists.openembedded.org/pipermail/openembedded-core/2017-August/141516.html