-
Notifications
You must be signed in to change notification settings - Fork 58
Prefer OS Specific Paths #474
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
Prefer OS Specific Paths #474
Conversation
We require contributors to sign our Contributor License Agreement, and we don't have yours on file. In order for us to review and merge your code, please send a signing request to cla-requests@gdlauncher.com and add your github handle to contributors list. |
This should also fix #468 I think |
I was reviewing this, and I remembered that I also wanted to use the platform's recommended cache directory for downloading and extracting modpacks. I was looking up the |
Alrighty, will do both soon today. |
Are we sure we don't want to use #[cfg(target_os = "macos")]
{
crate::BASE_DIRS
.home_dir()
.join(".config")
.join("ferium")
.join("config.json")
}
#[cfg(not(target_os = "macos"))]
{
crate::PROJECT_DIRS.config_dir().join("config.json")
} meanwhile we can only use the last block? Also, since we'll use system cache paths now, should I rename the old
and
to |
- Use system specific path for ferium caches too, and rename `.tmp` and `.cache` to more convenient names. - Use system specific path for config on macOS too. - Update documentations and README for these changes.
Yeah I would really prefer using the standard *NIX
Outside of Windows, one benefit of using this method is that we're now using XDG user directories on Linux.
Yep that would be great! |
From previous commit.
We require contributors to sign our Contributor License Agreement, and we don't have yours on file. In order for us to review and merge your code, please send a signing request to cla-requests@gdlauncher.com and add your github handle to contributors list. |
We require contributors to sign our Contributor License Agreement, and we don't have yours on file. In order for us to review and merge your code, please send a signing request to cla-requests@gdlauncher.com and add your github handle to contributors list. |
Ready for review. |
Reminder to self: add to changelog after approval. |
We require contributors to sign our Contributor License Agreement, and we don't have yours on file. In order for us to review and merge your code, please send a signing request to cla-requests@gdlauncher.com and add your github handle to contributors list. |
I used |
We require contributors to sign our Contributor License Agreement, and we don't have yours on file. In order for us to review and merge your code, please send a signing request to cla-requests@gdlauncher.com and add your github handle to contributors list. |
We require contributors to sign our Contributor License Agreement, and we don't have yours on file. In order for us to review and merge your code, please send a signing request to cla-requests@gdlauncher.com and add your github handle to contributors list. |
Thank you for the contribution! |
Seems like 9e04587 doesn't compile, just FYI in case its unnoticed. |
Co-authored-by: Ilesh Thiada <ileshkt@gmail.com>
Closes #470
This could be done in a better way, but for the sake of simplicity and not changing things too much, I preferred this way.