[Feature] Allow a systemwide Scoop install that still works within each individual user folder #5374
Replies: 3 comments 2 replies
-
I'm just trying to understand, what problem are you facing when installing Scoop for each user individually (i.e. in their respective home folders)? |
Beta Was this translation helpful? Give feedback.
-
I don't want to have to log in to someone's account to install scoop for them. For example, in an educational setting I want to prepare a few machines for use by multiple student users. I want each account created to be able to have access to Scoop automatically. Another example: on a domain-joined computer, I want developers to have access to scoop on any computer they happen to log in to, without having to install it manually each time. Sure, it might be easy to install it for the end user, but the convenience of it just being available automatically is a nice quality-of-life feature. I still use Scoop because it has plenty of apps that WinGet doesn't (and may never, with its limitations) have. But WinGet is built in to Windows and requires no installation. I want a similar seamless experience for users for Scoop on systems I admin. |
Beta Was this translation helpful? Give feedback.
-
I don't think this is possible, given the current architecture of Scoop. In fact, I'm not aware of any package manager (even on Linux/macOS) that allows this. You want a global package manager, but local packages. Even if winget is a global package manager, the packages it installs are also global. Here's an idea you could try: install Scoop on a global location, but then set the SCOOP environment variable for each user pointing to their respective home folders (more info on env vars here: https://github.com/ScoopInstaller/Install/). |
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.
-
Feature Request
Is your feature request related to a problem? Please describe.
I want to be able to have the
scoop
command available to all users on a system. However, I want the command to work for each user as if it were installed by that user locally - i.e. program installs go to each user's own home directory.I basically want to be able to preinstall Scoop on a machine, and then anyone who logs into that machine has access to use Scoop to install programs within their own user account without needing to install it themselves.
Describe the solution you'd like
Perhaps it already exists, but I haven't found anything obvious in the documentation for it.
Perhaps something like:
While for my use case being able to limit access to Scoop by user/group is unimportant, I'd imagine this would be important for some, so perhaps a consideration for how that would be handled.
Describe alternatives you've considered
I could maybe set up some sort of login script on a local machine for the DefaultUser account, but I'm a bit rusty on my Windows admin skills.
Beta Was this translation helpful? Give feedback.
All reactions