-
Notifications
You must be signed in to change notification settings - Fork 445
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
data_directory() and data_local_directory() are identical. #2212
Comments
I see the following code in the just codebase, in "data_directory" => Nullary(|_| dir("data", dirs::data_dir)),
"data_local_directory" => Nullary(|_| dir("local data", dirs::data_local_dir)), It therefore seems more than likely that it is the dirs crate that is at fault. |
Well, I looked into it. It seems that the dirs-rs crate always uses the user-space and not the system-wide values for folders. As such, it does not fit my use case. For instance, my As such, the python It's no biggie to invoke python from just. So not a big issue. But it is debatable whether just should only provide support for userspace folders. In fact, I'd suggest the following kind of nomenclature:
The rationale being that for things to work out of the box, it's better to have short names, and, in this case, there is no access rights issues for the short names. The longer names need an explicit decision (to type longer) stuff, and this is as such a warning that more pain is in order: no access rights for system folders by default. Any way. This is a design decision to make. |
If |
Hi.
As I'm busy making executable justfiles to my own end, they do require some auxiliary files (for templating with tera, in this case). So I've been playing with data_directory() and data_local_directory().
I noticed they both return something like
/home/mini-me/.local/share
. I would have expected something like/usr/local/share
for data_directory().Haven't looked into it. Can't tell whether just is at fault or if it is the dirs crate that is at fault.
Using just 1.29.1.
The text was updated successfully, but these errors were encountered: