Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: TheTuxKeeper on June 03, 2006, 03:35:40 pm
-
First it's a thought of Pascal Bleser (a suse packager), but I agree with him :)
console_runner is a very general name what could cause naming problems with other apps, because it's usually installed into a systemwide bindir. But even there won't be name conflicts you don't know to which app it belongs. Since it's part of codeblocks a more specific name like codeblocks_console_runner or cb_console_runner would be better.
What do you think ?
I only talk from a linux user's point of view. ;)
-
Agreed. I (gentoo-user) didn't have any such problem yet, but better we avoid it right now. I don't think that this would be a problematic change - or am I missing something?
-
First it's a thought of Pascal Bleser (a suse packager), but I agree with him :)
console_runner is a very general name what could cause naming problems with other apps, because it's usually installed into a systemwide bindir. But even there won't be name conflicts you don't know to which app it belongs. Since it's part of codeblocks a more specific name like codeblocks_console_runner or cb_console_runner would be better.
What do you think ?
I only talk from a linux user's point of view. ;)
Hello.
I did not have any troubles on Ubuntu and Gentoo until now, but as Der Meister said it is better to avoid them.
IMHO cb_console_runner is a good alternative :).
Best wishes,
Michael
-
I submitted a patch for this issue (I also posted it in the community patches thread): https://developer.berlios.de/patch/index.php?func=detailpatch&patch_id=1107&group_id=5358
I renamed the binary name of console_runner to cb_console_runner in sources, project files, *.iss, update scripts and Makefile.am (nearly everywhere I found it ;) )