Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include Chocolatey packages in releases #707

Closed
DustinVenegas opened this issue Jun 24, 2015 · 5 comments
Closed

Include Chocolatey packages in releases #707

DustinVenegas opened this issue Jun 24, 2015 · 5 comments

Comments

@DustinVenegas
Copy link

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.

@CharliePoole
Copy link
Contributor

This duplicates #452

Thanks for your comments. They will help us on implementing this.

@CharliePoole
Copy link
Contributor

Can you explain what you mean by NUnit.install and NUnit.portable?

@DustinVenegas
Copy link
Author

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.

@CharliePoole
Copy link
Contributor

Thanks. Can you point me to an example package that uses this convention?

@DustinVenegas
Copy link
Author

Thanks. Can you point me to an example package that uses this convention?

Sure! Putty has a virtual package, Windows Installer package, and bin deploy package.

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.

@rprouse rprouse modified the milestone: Closed Without Action Jan 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants