Naming conflicts

From GoboLinux Knowledge Base

This is a discussion page for package naming conflicts, both for different projects with the same name (rare) and GoboLinux packages with the same name which refer to the same project (more common, but let's work to extinguish this).

1 Basic conflict resolution guidelines
2 Conflict list
- 2.1 F
- 2.2 J
- 2.3 K
- 2.4 L
- 2.5 M
- 2.6 P

[edit] Basic conflict resolution guidelines

For the vast majority of programs, we can just take the project name as found in the program's tarball (ie, "name" in "name-1.0.tar.gz") and apply the Package Naming Guidelines).
When a project has a long and a short name (as in multi-word vs. acronym), we'll use the shorter name.
When still in doubt, let's look at the way other distributions name them, and follow the most common name.
Capitalization issues are less relevant now with the recent versions of Scripts and Compile. Therefore it's not necessary to list capitalization decisions here, though a capitalization form may be suggested when reporting a conflict of some other nature.
Report naming decisions on this page, and check here before making decisions.

[edit] Conflict list

[edit] F

Firefox - short name - not FireFox, not MozillaFirefox, not Mozilla_Firefox.

[edit] J

JACK - prefer acronym. Not Jackit or Jack-Audio-Connection-Kit

[edit] K

KDE-Libs, KDE-Base, KDE-Graphics and so on - not KDE. This way, it is easier to let each user decide which parts of KDE he or she needs. When compiling KDE, the correct order is: KDE-Libs, KDE-Base, <Other KDE-*>, KDE-Addons.

[edit] L

LibArt_LGPL - match other distros - not LibArt
LibStdC++ - stand-alone version of GCC's Standard C++ Library - use the corresponding GCC version as the version number. This is a custom package we build based on our GCC packages, so it makes more sense to keep this kind of version tracking instead of using the (not always reliable?) .so version.