-
Notifications
You must be signed in to change notification settings - Fork 451
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
Use standard locations for Tribler directories and files #299
Comments
I agree that the default downloads directory is a bit strange currently. The .Tribler location is fine by me, on windows I think its the correct location. |
Also add an uninstall script for Mac. Couldn't find it myself. |
@Pathemeous You just have to throw the app bundle to the trash. |
Friend of mine did that, the .Tribler in the home directory remained after the install. |
Ah, I see what you mean. Do you really need a script to remove a directory? |
Not so much for the action, but something that removes it automatically when the application is uninstalled would be nice. |
Can you trigger scripts when an app bundle gets deleted on OSX? |
I don't think it is possible to detect when an app got deleted and perform actions after that. I also think it's not a big problem since when I execute |
After 11 years, some things changed in our file management. Our files are now in the appropriate locations, and user data files can now be removed through the |
Instead of [user home dir]/.Tribler and [desktop]/TriblerDownloads, use standard locations.
For Linux, use Freedesktop.org standards, perhaps through PyXDG:
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
http://www.freedesktop.org/wiki/Software/xdg-user-dirs/
For Mac OS, I found this after a quick search:
https://developer.apple.com/library/mac/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html
For Windows, this looks like a good place to start:
http://msdn.microsoft.com/en-us/library/windows/apps/hh967755.aspx
The text was updated successfully, but these errors were encountered: