You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chocolatey is a machine package management, or desired state configuration, tool. It assists with managing machine-level applications similar to apt-get and yum.
Chocolatey currently has an outdated package for NUnit submitted by an individual contributor. I propose the project includes a set of Chocolatey packages in addition to the NUnit ones. It's possible to contact the Chocolatey administrators and add a few trusted NUnit contributors to maintain the packages.
To best provide the best experience to Chocolatey users three packages need to be managed. NUnit, NUnit.Install, and NUnit.Portable. This allows other Chocolatey packages to only depend on a version of the placeholder package and users to select if they prefer a bin or Windows installation. For backward compatibility the NUnit package should perform an installation through the NUnit installer.
Furthermore since NUnit already uses proper semantic versions we do not have to create a new set of packages and can instead just rev the package versions. Users that depend on NUnit2x can specify the major release version during installation. The actual package bundles should continue to be stored as releases on GitHub and will not need to be modified.
The text was updated successfully, but these errors were encountered:
The "Install" postfix denotes that a package uses a Windows installer under the covers while a "portable" package is just a bin deploy with the ability to add items to the chocolatey bin and path.
Anything that depends on Putty should use the virtual package. The portable and install packages let the user select exactly which they'd like to install. Regretfully it's not implemented yet.
Chocolatey is a machine package management, or desired state configuration, tool. It assists with managing machine-level applications similar to apt-get and yum.
Chocolatey currently has an outdated package for NUnit submitted by an individual contributor. I propose the project includes a set of Chocolatey packages in addition to the NUnit ones. It's possible to contact the Chocolatey administrators and add a few trusted NUnit contributors to maintain the packages.
To best provide the best experience to Chocolatey users three packages need to be managed. NUnit, NUnit.Install, and NUnit.Portable. This allows other Chocolatey packages to only depend on a version of the placeholder package and users to select if they prefer a bin or Windows installation. For backward compatibility the NUnit package should perform an installation through the NUnit installer.
Furthermore since NUnit already uses proper semantic versions we do not have to create a new set of packages and can instead just rev the package versions. Users that depend on NUnit2x can specify the major release version during installation. The actual package bundles should continue to be stored as releases on GitHub and will not need to be modified.
The text was updated successfully, but these errors were encountered: