-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
[Feature] Argument to only add Scoop to $PATH for the current session. #5574
Comments
When you put Scoop on portable drive, then:
Whichever method you use, you can benefit from #5544 For now: Just set environment via: e.g.:
|
How can I do this outside of Powershell? |
@HUMORCE I mean the environment set-ing, could it be done with |
powershell profile? Scoop can't get SCOOP_ROOT_DIR from a relative path because #5544 hasn't been merged yet. so we must setup What I would do if I place Scoop on portable drive:
Then executing Or alter:
If a drive is mounted with different drive letter each time, I am sure it will have negative effects. |
What might those side-effects be? I want to consider this before setting it up, incase switching to a natively portable alternative (I still haven't found one without some gotchyas,) would be a better idea. |
Suggestion: mount drive as same drive letter on each PC. e.g. W, X, Y, Z |
@HUMORCE I mean without Powershell as in with a .bat or .cmd script. Or maybe this powershell script can be run with that to set the env? |
Yes |
After successfully installing scoop, installing anything breaks stuff, like a lot of stuff. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Feature Request
Is your feature request related to a problem? Please describe.
I would like to be able to run Scoop on a USB flash drive in a portable manner. Although I haven't tried to do this yet, I predict that there would be a PATH pollution problem. This could happen because Scoop adds itself to the PATH of the machine, not just for the duration of the terminal session, but forever.
Describe the solution you'd like
I would like to be able to run Scoop with an argument such as
--add-to-path-temporarily
which would silently exit after adding itself to the$PATH
environment variable for the duration of the session. In case of an error, it would log it to standard output and to any applicable log files.Describe alternatives you've considered
Maybe an alternative would be to remove any pollution afterwards with a script or something of the like, though this does add unneeded complexity that could be avoided if this could be prevented in the first place.
The text was updated successfully, but these errors were encountered: