Adding support for WinGet
-
@theopenem_admin I use powershell scripts to install applications:
https://github.com/Romanitho/Winget-Install
And for updates:
https://github.com/Romanitho/Winget-AutoUpdate
In modules and it works very well. -
I hope there will be some kind of hint if the package is installed in user/machine scope.
-
@eruthon
How would you envision a user scope winget working? Theopenem really doesn't handle users. So it would either install under machine scope, or you could set it as a login policy which would run under the user, but that would mean it run for every user that logs in, at login. -
@theopenem_admin
It's just that some package installers are exclusively machine-wide or just user-wide.I mean if you'd run winget command with impersonation account (which I'm doing, because winget couldn't be installed via system account), without specifying machine-wide argument you'd get what's default for the package, i.e. user-wide installation in some cases.
And as some packages aren't configured for machine-wide installation it created a problem for me.
That's why I pointed out if there's going to be some kind of hint if the package is machine- or user-wide installation.
Because I haven't seen that kind of hint in winget itself and you're probably more invested in its research than me.That said I don't really need user scope to work via TOEM. Just wondering if there will be any kind of info regarding the scope used for the package in some neat GUI info panel. It's just an idea to visually enhance the tool you develop.
-
No problem. I can easily add that info about package to the GUI.
-
I've got the server part mostly done, just need to do the client now. Here is how it looks.
All packages are searchable with some filtering options, clicking details shows this simple modal.
Any thoughts or suggestions?
-
@theopenem_admin
It looks great and the modal is interesting, do you plan to use it in other places of the web, too? -
@theopenem_admin Hi it would be possible to add support for chocolatey packages
-
@cycy
I thought chocolately wasn't meant for organizational use? They also seem to ban ip's for an hour once a limit of 20 is hit?https://docs.chocolatey.org/en-us/community-repository/community-packages-disclaimer
-
@eruthon
Eventually will be doing a minor UI refresh that will probably incorporate more of this type of navigation. -
This is now available in 1.5.6
-
@theopenem_admin
Is the --scope machine hard-coded into TOEMS when installing with winget modules? Some packages cannot get installed with it and practically I have no way of overriding this option, because --scope user doesn't work, too. -
It runs as machine scope unless the trigger is set to login. I haven't been able to get it to run any other way. You should be able to set the scope in the override field, but I still haven't been able to get it to work.
-
@theopenem_admin Yeah i get that, but I found a program, which installs only without specifying any scope in the command. I guess it's a problem of the package maintainer, but it's better to have us as system admins specify, which scope we wish to apply from e.g. a drop-down menu in the winget module.