Replies: 4 comments 2 replies
-
This will be achievable once #1813 gets fixed |
Beta Was this translation helpful? Give feedback.
-
if I understand #1813- it is about create a %SCOOP_PATH% env variable instead of manipulating the user %PATH% again & again. My Intention is to "localize" the apps to a project scope: |
Beta Was this translation helpful? Give feedback.
-
can we revisit this? When next version #5424 will land, it is look doable with the portable config file (feat(config): Support portable config file #5369). I did some changes to the install script, and from initial tests it is "kind" of working- see here Of-course there are changes required in the
But let see first, if this is something that we want. |
Beta Was this translation helpful? Give feedback.
-
If anyone want to test/play with more than one scoop location on the same machine, I have it working. The work is based on #5369 & #1813 (no PR yet although it is working here). To install a second location of
You will need to use repo: https://github.com/hagaigold/Scoop, with branch:
You should see something like that:
Next:
If all gone well, you should have now, some new options for the
Your new scoop location should be setup in PATH and ready to use.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Maybe this is out of the scope of the amazing scoop project, but I wonder if someone tried to use scoop for a limited scope.
Think of modules dependencies for a project that I want to be "locally" to the project instead to install it in the "all" user space.
A real-life example: Lua project scripts for Clink.
I aware about git submodules and alike- I just like the simplicity of scoop to fetch anything from git.
happy day
Beta Was this translation helpful? Give feedback.
All reactions