(nodejs16) Migrate package

[AdmiringWorm]

Discussed in #2060

^{Originally posted by tomchiverton November 10, 2022}
I was asked by the community reviewers of my own package of Nodejs v16 to see if you would consider shipping it - essentially just a meta package that depends on the latest v16 release.

There's clearly a need for a package that pins a particular supported upstream major version, rather than tracking the latest and greatest LTS.

Their view is that ss the Chocolatey Community Chocolatey Packages repository maintains the nodejs package, I think it would make sense for this package to be owned there too.

Would you be interested in taking it on ? Attaching the meta package file here for discussion on it if required.

If not, hopefully the review team would except it independently.

nodejs16.nuspec.txt

[tomchiverton]

Happy to submit a PR. Which folder do I need to drop a nodejs16.nuspec.txt (if that is the right name) in ?

[AdmiringWorm]

It depends on whether we would want to have this as an automatic package, or a manually updating one.

If there are no new updates for 16.x ever coming in the future, it is fine to have it as a manual package. In that case, just create a nodejs16 folder in the manual folder and drop the nuspec file in there (rename it to nodejs16.nuspec with out the .txt extension).

I haven't looked over the file itself, that will be done as part of the PR review.

If there will be updates in the future for that major version, we would need to have it as a automatic package. Similar procedure just in the automatic folder instead, but additionally a update.ps1 file is needed in that case so the appveyor build server will check for updates (take a look at the original nodejs.install/nodejs package in that case for the update script).

[pauby]

@tomchiverton Have you made any progress on the PR?

[tomchiverton]

#2122