Bug 11592

Summary:	Add QA check for uppercase recipe names
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Paul Eggleton <bluelightning>
Component:	core	Assignee:	yeoh ee peng <ee.peng.yeoh>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	costamagnagianfranco, dl9pf, meta.mr.watcher, meta.watcher, sgw, zuloch
Version:	2.3
Target Milestone:	2.4 M3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Yes (doc changes required)

Description Paul Eggleton 2017-05-30 10:24:10 UTC

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.

Comment 1 Lorenzo Chianura 2017-07-18 13:23:24 UTC

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.

Comment 2 yeoh ee peng 2017-08-15 07:29:59 UTC

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.

Comment 3 yeoh ee peng 2017-09-04 02:16:17 UTC

Patch to check recipe uppercase in insane.bbclass submitted to openembedded-core and it was accepted.

Comment 4 Gianfranco 2017-09-08 14:33:15 UTC

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

Comment 5 yeoh ee peng 2017-09-15 01:56:42 UTC

Pushed commit to mailing list for review:

http://lists.openembedded.org/pipermail/openembedded-core/2017-August/141516.html