Bug 3124 - yocto-bsp must not accept BSP names with spaces
Summary: yocto-bsp must not accept BSP names with spaces
Status: VERIFIED WONTFIX
Alias: None
Product: Eclipse Plugin
Classification: Yocto Project Subprojects
Component: eclipse-plugin (show other bugs)
Version: 1.3
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.4 M1
Assignee: Jessica
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-09-18 08:08 UTC by Alexandru Georgescu
Modified: 2013-04-17 13:57 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Georgescu 2012-09-18 08:08:53 UTC 
In yocto-bsp main page, the field "BSP Name*" accepts spaces. Since BSP names cannot accept spaces but only "_", "-" and ".", a check must be put in the page to prevent the user adding one.
Comment 1 Jessica 2012-11-29 19:43:20 UTC 
commit	f12b8fae90e4b6d62119277d4484cbb939f73edd
Comment 2 Alexandru Georgescu 2012-12-10 08:12:52 UTC 
Hi Jessica,
Indeed, the BSP Name does not accept spaces, but it accepts other characters like:  !@#$%^&*()_+{}"|<>?.

Since being able to add those characters to the BSP name but getting error when trying to create one BSP, I am reopening this.
Comment 3 Jessica 2012-12-12 00:02:42 UTC 
Hi Alex,

I think there should be only one place to check the validity of bsp name which is the yocto-bsp script itself.  Otherwise, we may always have the sync issue from eclipse side with the script.  If you found that the yocto-bsp script report an error and it's not reflecting to the user, then I think that's a more appropriate bug to fix.  BTW, I've tested with your special character list, seems the even the yocto-bsp script will take ? and # as BSP names.
Comment 4 Alexandru Georgescu 2013-04-17 13:57:16 UTC 
Verified as per above comment.