Replies: 2 comments 1 reply
-
Hi, could you post your feedback in the issue tracker - here #1813? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Okay, it seems we are destroying users Lines 6 to 9 in aa3826c Brought to attention via #5395
This needs to be implemented in the installer and Scoop itself:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I recently started to use
scoop
at my work computer, and I have environment variables that I need to include in thePATH
to use some tools thatscoop
can't manage. However, every time that I runscoop update --all
orscoop cleanup --all
, all my variables included in thePATH
are changed for their absolute paths. It is troublesome because some of that variables need to be changed at runtime.So, I don't know the impact of this suggestion to the whole project, but... why
scoop
doesn't use environment variables (that can be included in thePATH
) and update them, instead of put the applications' paths directly in thePATH
, refreshing it and killing every variable's reference?Individual environment variables for each app, depending on the quantity of apps to include in the environment, could be troublesome to manage. However, working in that way could avoid problems of compatibility with other apps that are not managed by
scoop
.A complementar suggestion: to declare a
SCOOP_APPS_PATH
variable, and include allscoop
managed's apps in it, and then do reference to it in thePATH
variable.Beta Was this translation helpful? Give feedback.
All reactions