Neos-Metaverse / NeosPublic

A public issue/wiki only repository for the NeosVR project
194 stars 9 forks source link

Neos Public build in PM such as chocolatey #3282

Open kazu0617 opened 2 years ago

kazu0617 commented 2 years ago

Is your feature request related to a problem? Please describe.

Neos cannot currently be installed via PM (at least not via chocolatey).

Relevant issues

This story may be closely related to Neosine, but I'm pretty sure NeoSine doesn't have such a release for PM at the moment. https://github.com/Neos-Metaverse/NeosPublic/projects/6#card-68054524 https://github.com/Neos-Metaverse/NeosPublic/projects/6#card-68054394

EDIT: There was an Issue that asked if we could make it a nuget package. However, as far as the content is concerned, it is supposed to be a feature for plugin developers, which is different from the purpose of this issue. https://github.com/Neos-Metaverse/NeosPublic/issues/1430

Describe the solution you'd like

Push Neosine launcher or Neos Latest Public build push in chocolatey, which allow install with package.

When I heard that Neos was going to be distributed outside of Steam, I checked on chocolatey to see if they were distributing it, but they are not at the moment, and I thought if they did, it would be possible to install Neos with a single command line.

Describe alternatives you've considered

I could make myself a package manager and get the builds from Steam and manage the packages, but I'm not sure if I'm allowed to do that (some packages have no choice but to do that, so if I'm allowed to do that, I will).

Additional context

No response

iamgreaser commented 2 years ago

My mind has been going from "yes" to "no" to "yes" to "no" and all around with this idea. So that's why I've been doing :+1: and then removing it.

The best model for this is probably along the lines of how Steam ends up in package managers on Linux distros. You can get Steam from your package manager, but it's a bootstrapping environment, and it's intended that it obtains the latest version of Steam itself and keeps itself updated while sitting around in a "hidden" directory in your home directory (typically ~/.local/Steam/).

If you do something like this, and you can distribute it over Chocolatey, that could work quite well.

This does rely on Neosine being able to update itself, of course.

clarjon1 commented 2 years ago

Having it available in something like chocolatey would also be beneficial for corporate and educational environments, with sysadmins who already employ this tooling for managing installation of various required applications to add neos to the list so it's available and ready for their end users

Nytra commented 2 years ago

There is also the official "Windows Package Manager CLI" from Microsoft, which could offer an alternative to Chocolately https://github.com/microsoft/winget-cli

sveken commented 2 years ago

Plus one for the official one, Another third party one is Ruckzuck which integrates into SCCM (if we are talking about corporate/education environments)