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

Allow custom installation location #1009

Open
shpoont opened this issue May 12, 2024 · 4 comments
Open

Allow custom installation location #1009

shpoont opened this issue May 12, 2024 · 4 comments

Comments

@shpoont
Copy link

shpoont commented May 12, 2024

Since pkgx install is simply checking if the user has permissions to write to /usr/local it has a very confusing behavior. When there are more than one users in the system it will have conflicting results because some packages can be already installed by another user to the same folder.

It would be useful to have a simple PKGX_INSTALLATION_DIR showing it where to install/uninstall packages.

@felipecrs
Copy link
Contributor

felipecrs commented May 13, 2024

I would say even pip, npm, cargo and whatnot should also be patched to respect this environment variable (when installed by pkgx).

@mxcl
Copy link
Member

mxcl commented Sep 6, 2024

I wonder if there is some appropriate env var that already is established.

@felipecrs
Copy link
Contributor

felipecrs commented Sep 6, 2024

Some examples I know:

DENO_INSTALL_ROOT: deno install --global will install "binaries" to to $DENO_INSTALL_ROOT/

https://docs.deno.com/runtime/manual/basics/env_variables/

CARGO_INSTALL_ROOT: cargo install will install binaries to $CARGO_INSTALL_ROOT/bin/

https://doc.rust-lang.org/cargo/commands/cargo-install.html#description

@mxcl
Copy link
Member

mxcl commented Sep 7, 2024

$PKGX_INSTALL_ROOT seems appropriate then, and perhaps we dare try to standardize on $INSTALL_ROOT as a secondary lookup.

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

3 participants