Skip to content
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

feat: Add xdg_basedir module to respect XDG Basedir spec even on macOS #40

Closed
wants to merge 1 commit into from
Closed

Conversation

poliorcetics
Copy link

This is mostly useful for CLI tools and people who want to have their config files in the same
place on both macOS and Linux, making it much easier to save them in a VCS repo.

This is mostly useful for CLI tools and people who want to have their config files in the same
place on both macOS and Linux, making it much easier to save them in a VCS repo.
@poliorcetics
Copy link
Author

Follow up works will need to be done on https://github.com/dirs-dev/directories-rs to support it nicely.
Since the changes here are not API breaking, a minor version can be released and used in directories

@soc
Copy link
Collaborator

soc commented Apr 25, 2022

Sorry, as mentioned in the original issue, I don't think this is a good idea.

The dirs crates are intended to follow platform rules, not invent their own conventions.

Not following the OS rules due to being a CLI tool sounds like a reason just as bad as the dozen other excuses people come up with to litter $HOME with their application folders. (Which is the reason we are in this mess in the first place.)

Not to mention the additional confusion and support requests this will cause.

If you want XDG rules use Linux, if you want Apple rules use a Mac.

@soc soc closed this Apr 25, 2022
@poliorcetics
Copy link
Author

The slew of requests asking for this on macOS seems to indicate a need exists for this feature, just as the number of Rust CLI tools that entirely bypass this crate and use another way to get support for the XDG spec on macOS

@soc
Copy link
Collaborator

soc commented Apr 25, 2022

entirely bypass this crate and use another way to get support for the XDG spec on macOS

That's what I generally recommend. It doesn't make sense to use a crate that follows the rules of the operating system, while trying to avoid the rules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants