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

Consider using ~/.local/bin in addition to (or instead of) ~/.ozy/bin #15

Open
apmorton opened this issue Sep 22, 2020 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@apmorton
Copy link
Contributor

~/.local/bin is defined as part of the systemd file-hierarchy

Any distro that uses systemd (or makes an attempt to be compatible with systemd conventions) will recognize this directory and place it on the users path upon login if it exists.

Note that this path is not guaranteed to exist, so you may need to create it upon first use.
On a similar note, this path will not appear on $PATH if it does not exist, so you may need login-cycle after creating it.

Using ~/.local/bin decreases $PATH bloat, but it also means you may conflict with binaries placed by others.
These potential conflicts already existed in the logical sense that weird and unexpected things may happen depending on order within $PATH, but now they become "that file already existed" issues when placing symlinks.

@mattgodbolt mattgodbolt added the enhancement New feature or request label Sep 22, 2020
@mattgodbolt
Copy link
Contributor

Thanks @apmorton!

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

No branches or pull requests

2 participants