ironpython3 icon indicating copy to clipboard operation
ironpython3 copied to clipboard

Correct and publish Cocolatey package

Open BCSharp opened this issue 3 years ago • 1 comments
trafficstars

From the discussion on Gitter:

slozier
@slozier
[May 02 13:49](https://gitter.im/IronLanguages/ironpython?at=627043d789dcc96e9ce3095b)
I didn't publish to chocolatey. I wasn't sure if it should be a new package (e.g. ironpython3) or just publish as ironpython... Probably the latter since 2 is basically done
Pavel Koneski
@BCSharp
[May 02 15:04](https://gitter.im/IronLanguages/ironpython?at=62705581d30b6b44ebcd3af1)
CPython publishes python (last 2.10.4), python3 (same) and pytyhon2 (last 2.7.18). The plain python contains both 2 and 3 versions. So I'd say, yes, publish it as ironpython. If you ever need to publish yet another 2, then maybe create a new "legacy" package named ironpython2.
Pavel Koneski
@BCSharp
[May 02 15:48](https://gitter.im/IronLanguages/ironpython?at=62705fb1d4ef6e15af29949a)
typo 2.10.4 => 3.10.4
slozier
@slozier
[May 03 16:57](https://gitter.im/IronLanguages/ironpython?at=6271c17510cfc315bc6137c4)
Hmm, the package was built with the id ironpython3. Guess I'll have to patch it to publish as ironpython.
slozier
@slozier
[May 03 16:58](https://gitter.im/IronLanguages/ironpython?at=6271c1a746495f47cfc3c043)
Don't think I'll have time to look at it tonight, but please remind me if I forget about it.

BCSharp avatar May 24 '22 18:05 BCSharp

Thanks for the reminder. I updated the nuspec in https://github.com/IronLanguages/ironpython3/commit/5d98bd8ed243649981ae6719bce94780d9e39d8d. I think I may hold off for 3.4-final before publishing (since it's most likely going to happen this summer). Unless you feel strongly about getting the beta on Chocolatey...

slozier avatar May 29 '22 00:05 slozier

Can this be closed now?

BCSharp avatar Dec 21 '22 16:12 BCSharp

Yep!

slozier avatar Dec 21 '22 18:12 slozier