Reproduction: Create XULrunner app with application.ini containing: [App] Vendor=Ben Bucksch Name=IT Shop Actual result: xulrunner creates ~/.ben\ bucksch/it\ shop/profile.ini Expected result: xulrunner creates ~/.xulrunner/benbucksch/itshop/profile.ini or ~/.xulrunner/itshop/profile.ini Rationale: When I create a xul app, the vendor is "Ben Bucksch". However, it doesn't make sense for me to have a /home/ben/.ben bucksch/ for xul apps. In fact, it doesn't make much sense for users either. (I realize it does make sense for .mozilla/firefox/.) Compare KDE, they also put app profiles in .kde/.
Compare bug 365023 about the spaces.
Summary: xulrunner app profiles should be in ~/.xulrunner → xulrunner app profiles should be in ~/.xulrunner/
I disagree. XULRunner is an implementation detail: there's no need include that in a profile directory name.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WONTFIX
> XULRunner is an implementation detail That's right. But so are almost all of the contents of the profile directory. What do you propose for the ridiculous /home/<user>/.benbucksch/<appname>/?
Actually, I think we're touching a broader issue here. It's right to have a single place to define vendor and appname. However, there are different variations of them. Some differ only in format (e.g. capialization or allowed characters) and might be transformed automatically (see bug 365023), some may be different in content. For example, the copyright, supplier and responsible party is the legal name "Take Two Game Systems, Inc", which is cumbersome, long and may actually change, while the otherwise used name (e.g. displayed and encoded) is the brand name "Take Two". Similarly, for some products, the full name is Vendor name + application name (e.g. "Nescape Navigator"), while for others the full name is a certain form of only the application name ("Mozilla", "Seamonkey" etc.). This may be one of these cases. I am the creator, but my name does not appear in the product name.
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.