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

rust pkg should follow freedesktop base directory specification under appropriate platforms #6425

Closed
mstewartgallus opened this issue May 11, 2013 · 5 comments

Comments

@mstewartgallus
Copy link
Contributor

Currently rust pkg creates a dot directory in the home directory under certain platforms. This really bothers me, and I think it'd be nice if once of the options listed under here were followed instead http://freedesktop.org/wiki/Specifications/basedir-spec

I'm really not sure which option listed there is best but I feel any of them would be better than the current approach.

@thestinger
Copy link
Contributor

it would go in $XDG_DATA_HOME

@metajack
Copy link
Contributor

I assume you mean $XDG_DATA_HOME which is by default .local/share.

I'm pretty sure other tools ignore this guideline and use directories directly under $HOME. For example, Maven uses ~/.m2 and Ruby gems are in ~/.gems.

@z0w0
Copy link
Contributor

z0w0 commented May 12, 2013

I'm going to disagree here. The directory is only created under the current directory when working in a workspace, it's no different to node_modules or .git. The only other way would be to copy the entire workspace over to a unique directory in $HOME which is ugly.

@catamorphism
Copy link
Contributor

In incoming, rustpkg no longer creates a .rustpkg directory anywhere (though one of the help messages still mentions one; I should clean that up.)

@catamorphism
Copy link
Contributor

BTW, https://github.com/mozilla/rust/blob/master/doc/rustpkg.md describes the expected directory structure for a workspace.

flip1995 pushed a commit to flip1995/rust that referenced this issue Jan 30, 2021
Closes rust-lang#6425

Looks for ends_with methods calls with case sensitive extensions.
flip1995 pushed a commit to flip1995/rust that referenced this issue Jan 30, 2021
…sions, r=llogiq

Case sensitive file extensions

Closes rust-lang#6425

Looks for ends_with methods calls with case sensitive extension comparisons.

changelog: Add new lint that warns about case-sensitive file extension comparisons.
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

No branches or pull requests

5 participants