to Chocolatey. No new comments since February 9 despite three relists. (non-admin closure) –LaundryPizza03 (dc̄) 00:46, 12 March 2023 (UTC)
OneGet is a very separate tool that isn't related to NuGet. OneGet is the predecessor to PowerShellGet and can be installed with NuGet. NuGet had no previous names called "OneGet". See https://github.com/OneGet/oneget Aaron Liu (talk) 20:17, 27 January 2023 (UTC)
:"OneGet" was renamed "PackageManagement" on Mar 20, 2015, as mentioned on GitHub (/OneGet/oneget/ link above) and at Chocolatey ("In April 2014, Microsoft debuted OneGet (later renamed PackageManagement) alongside PowerShell 5.")
:On 2016-06-24, I created both OneGet and PackageManagement as redirects to NuGet (which is consistent, but apparently wrong). (I don't recall why.)
:PowerShell#Windows_PowerShell_5.0 mentions OneGet (and Chocolatey).
:PowerShell#Windows_PowerShell_5.1 mentions PackageManagement.
:PowerShellGet is not even mentioned on Wikipedia, though it seems important ("PowerShellGet is the package manager for PowerShell"). "Windows PowerShell 5.1 comes with version 1.0.0.1 of PowerShellGet preinstalled. .... PowerShell 6.0 shipped with version 1.6.0 of PowerShellGet. PowerShell 7.0 shipped with version 2.2.3 of PowerShellGet. The current supported version of PowerShellGet is 2.2.5. If you are running Windows PowerShell 5.1, you must install a newer version." (https://learn.microsoft.com/en-us/powershell/module/PowerShellGet/?view=powershell-7.3&viewFallbackFrom=powershell-7) PowerShellGet dates back to 2016! (https://www.powershellgallery.com/packages/PowerShellGet/2.2.5).
:Is Microsoft changing everything so fast that users and Wikipedia can't keep up with it?
:I was wondering why you couldn't "just fix" this. But I don't see a fix. They could just re-redirect to PowerShell, or just be deleted because they have nowhere to go...
:Is PowerShellGet connected to OneGet/PackageManager or is it a separate start? (This seems like a familiar MS clusterf....)
:Should PowerShellGet get a new article (is it notable?)? Then PowerShellGet could mention OneGet/PackageManagement as (irreplaceable and actively maintained?) (abandoned? semi-compatible? predecessors?) that they are? -A876 (talk) 21:14, 27 January 2023 (UTC)
::The OneGet people left the project to go work on PowerShellGet. So the latter is essentially a spiritual successor.
::I'm not sure how to deal with this either, hence why I've brought this to RfDiscussion. One choice is to expand the redirect into an article but I'm not sure if OneGet passes notability (I didn't find much coverage of it)
::Also, nice edit summary. Aaron Liu (talk) 21:25, 27 January 2023 (UTC)
:While we're here on this uninvolving subject, how do recent developments affect the relevance of OneGet / PackageManagement? Are these and other package managers only resorted-to by users of Windows pre-10? Do all the package managers in this lovely ever-growing garden jungle of package-managers-of-the-week clash, or do they calmly share repositories, co-exist on computers (under any new or old operating system and real or virtual platform), wasting only disk space, registry space, and human minds and lives? How many new ways of conflict/malfunction/failure do they create? Is every new package manager a deep accomplishment or merely yet another trivial mashup (any repository client + any .exe / .msi launcher)? Will users soon need package-manager manager packages? (This must end somewhere.)
:{{Quote frame|The Windows Package Manager (also known as winget) is a free and open-source package manager designed by Microsoft for Windows 10 and Windows 11. It consists of a command-line utility and a set of services (no less?) for installing applications Independent software vendors can use it as a distribution channel for their software packages. (until screwed again?)
...
Before deciding to develop Windows Package Manager, the team behind it explored Chocolatey, Scoop, Ninite, AppGet, Npackd, and the PowerShell-based OneGet. After the announcement of winget, the developer of AppGet, Keivan Beigi, claimed that...}}
:— Preceding unsigned comment added by A876 (talk • contribs) 17:23, 30 January 2023 (UTC)
:I’m pretty sure OneGet was for windows 10. It was also bundled in it. I’m also pretty sure that OneGet was the "package manager manager". Aaron Liu (talk) 16:46, 31 January 2023 (UTC)
- Retarget to Chocolatey which has a good description of OneGet. Jay 💬 14:30, 4 February 2023 (UTC)
- :@Jay It does, yet I wonder why it was even included. The chocolatey article doesn’t seem to be suitable housing for oneget information since their only relation is that oneget browses the chocolatey repository. Should that information even be in the chocolatey article in the first place? Aaron Liu (talk) 14:45, 9 February 2023 (UTC)
- ::I am willing change my vote depending on what changes are made at Chocolatey before this RfD concludes. Jay 💬 15:07, 9 February 2023 (UTC)
:
{{resize|91%|Relisted to generate a more thorough discussion and clearer consensus.}}
Please add new comments below this notice. Thanks, CycloneYoris talk! 01:49, 9 February 2023 (UTC)
:
{{resize|91%|Relisted to generate a more thorough discussion and clearer consensus.}}
Please add new comments below this notice. Thanks, Timothytyy (talk) 11:05, 21 February 2023 (UTC)
:
{{resize|91%|Relisted to generate a more thorough discussion and clearer consensus.}}
Relisting comment: Final relist. More opinions are welcome.
Please add new comments below this notice. Thanks, Timothytyy (talk) 04:13, 1 March 2023 (UTC)
:The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on an appropriate discussion page (such as the redirect's talk page or in a deletion review).