-
-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flatpak misses app-name rules #50
Comments
Its not true that there are no app names rules. They have to be valid dbus names, and in fact, if you're using dbus in your app you need to have the same app name as dbus name for things to work. This means that its complicated for many of the above names to change, since they have pre-existing dbus names which are a form of ABI. However, I guess we should give some kind of recommendation for new apps. I wonder if there is some recommendation for dbus? @smcv do you know of any? |
The prefix is a domain that you own/control, and the suffix is up to you. That's the extent of the rules. "You" might mean an individual, a company/corporation, or a community like GNOME. It seems to be vaguely conventional that the prefix indicating the namespace (author, publisher, etc.) is all-lowercase, and the part indicating the project within that namespace has initial caps; so org.gnome.Evince is "Evince as defined by gnome.org", and org.freedesktop.Telepathy.AccountManager is "Telepathy.AccountManager as defined by freedesktop.org". That isn't a strict rule or anything though. |
In particular this means you can't use hyphens. You can use underscores, but it's relatively unconventional to do so. In the corner cases where you have a domain name that isn't a syntactically valid D-Bus name, I'd recommend replacing |
Not sure there's anything to fix here. Somebody could send a request to add that 'corner-case' recommendation to the docs at flatpak.readthedocs.io |
Some app names start with capital some lowercase.
On http:https://flatpak.org/developer.html there isn't some name ruling for the packaging. Should be camel case, hyphen split, all lower-cases etc?
The text was updated successfully, but these errors were encountered: