Advanced search
Log In
New Account
Home My Page Project Cloud Code Snippets Project Openings ESbox
Summary Forums Tracker Lists Tasks News SCM Files Wiki

Bugs: Browse | Download .csv

[#4729] Project naming principle

Please login

2009-10-26 10:42
Submitted By:
Henry Ovaskainen (henryov)
Assigned To:
Ed Swartz (eswartz)
Project naming principle

Detailed description
Do we have any chance to do some kind of check for the valid project name in project creation phase? E.g. If the name
of the project starts with numbers, it can cause various errors during building/debian package creation.

Feel free to discard :)

One example here, project name is 2MAEMOMM_EXAMPLES3
run "make"

*** exited with code 0

./configure: line 1: ${2MAEMOMM_EXAMPLES3_CFLAGS+set}: bad substitution
./configure: line 1: ${2MAEMOMM_EXAMPLES3_CFLAGS+set}: bad substitution
./configure: line 1: ${2MAEMOMM_EXAMPLES3_LIBS+set}: bad substitution
./configure: line 1: ${2MAEMOMM_EXAMPLES3_LIBS+set}: bad substitution
./configure: line 1948: 2MAEMOMM_EXAMPLES3_RELEASE=2maemomm_examples3_major_version.2maemomm_examples3_minor_version:
command not found
checking for a BSD-compatible install... /scratchbox/tools/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output file name... 
configure: error: C compiler cannot create executables
See `config.log' for more details.

*** exited with code 77


sbox-arm-none-linux-gnueabi-gcc: '-V' must come at the start of the command line
configure:2795: $? = 1
configure:2818: checking for C compiler default output file name
configure:2845: gcc -O2 -g   conftest.c  >&5
conftest.c:7:9: error: macro names must be identifiers
conftest.c:8:9: error: macro names must be identifiers
conftest.c:9:9: error: macro names must be identifiers
conftest.c:10:9: error: macro names must be identifiers
configure:2848: $? = 1
configure:2886: result: 
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME "2maemomm_examples3"
| #define PACKAGE_TARNAME "2maemomm_examples3"
| #define PACKAGE_VERSION "2maemomm_examples3_version"
| #define PACKAGE_STRING "2maemomm_examples3 2maemomm_examples3_version"
| #define 2MAEMOMM_EXAMPLES3_MAJOR_VERSION 2maemomm_examples3_major_version
| #define 2MAEMOMM_EXAMPLES3_MINOR_VERSION 2maemomm_examples3_minor_version
| #define 2MAEMOMM_EXAMPLES3_MICRO_VERSION 2maemomm_examples3_micro_version
| #define 2MAEMOMM_EXAMPLES3_VERSION 2maemomm_examples3_version
| #define PACKAGE "2maemomm_examples3"
| #define VERSION "2maemomm_examples3_version"
| /* end confdefs.h.  */
| int
| main ()
| {
|   ;
|   return 0;
| }
configure:2893: error: C compiler cannot create executables
See `config.log' for more details.


Date: 2009-11-27 07:54
Sender: Juha  Hentunen

Verified using build mica_esbox_pluthon_3.4.2_build.618.
Date: 2009-11-06 21:27
Sender: Ed Swartz

This is fixed in Mica rev 3297.  Note that the package name is
canonicalized to work, but the project name is still allowed
to be whatever you entered.

The logic is, we take the "base name" from the project,
which is the biggest embedded sequence of A-Z, 0-9, and dashes.

The package name only retains the A-Z and 0-9 characters and
adds "package" to the front if it starts with a number.

The package name is used both in Debian package rules and in
variables used by autotools.

So, validate this by looking in, e.g., debian/control and

Date: 2009-11-06 13:54
Sender: Ed Swartz

This is probably a good bug to fix, because it's difficult to
change the package name after the project is created.
Date: 2009-10-27 10:31
Sender: Ilja Pyykkonen

There is also problem creating Debian structure from template
(new project) when project name contains dash "-".
The Debian package creation fails to syntax error.

The create Debian package structure seems to work fine with dash
in project name.

Attached Files:

Name Download
No Files Currently Attached


Field Old Value Date By
ResolutionFixed2009-11-27 07:54juhentun1
ResolutionAccepted as a Bug2009-11-06 21:27eswartz
ResolutionNone2009-11-06 13:54eswartz
Severityenhancement2009-11-06 13:54eswartz
assigned_tonone2009-11-06 13:54eswartz
File Added645: invalid_project_name.txt2009-10-26 10:42henryov

Terms of Use    Privacy Policy    Contribution Guidelines    Feedback

Powered By GForge Collaborative Development Environment