briandfoy/rakudo-star-chocolatey

Rakudo Star chocolatey packages

rakudo-star-chocolatey's Issues

Get the SHA256 checksum automatically

Feature request: Paid support proposal

I try to have my published Raku modules (40+) be usable on Windows, but I am not an active Windows user, nor do I have a Windows host capable of installing anything newer than MS Pro 10.

In order to help spread the use of Raku to the wide world of Windows, I would like to financially help. I have to go now, but, if interested, please email me at [email protected]. I'm @tbrowder on Github and IRC channel #raku.

Convert tests to Raku

Automate new Rakudo detection

• Check the website and notice a new file
• Modify the appropriate files
• Test the package
• push the package

xmllint the nuspec file

Create a Makefile

Codify the steps in make and let this be a single command bit of work.

• An all step to build the package and everything else without pushing
• A push target to finish it all
• A test target

Convert programs in bin/ to Perl 6

Don't necessarily replace the ones that are there, but do the same thing with a .p6 extension.

Rakudostar on chocolatey is outdated

Hi brian,

rakudostar on chocolatey is in version 2019.03.01 while last release is 2020.07.1
could you sync an update.
thanks, regards.

set up AppVeyor testing

Perhaps a useful example: https://github.com/AdmiringWorm/chocolatey-packages/blob/master/.appveyor.yml

Create the nupkg file automatically

Or, do whatever choco pack does but without choco. My actual goal is to be able to do things directly from a Unix environment, or at least my Mac. My particular problem is that I'm not on Windows and I start a VM to work with that. I'd like to have something that doesn't require a VM.

choco will run on Mono, so a solution might be to merely install Mono.

• http://www.onitato.com/running-chocolatey-on-linux.html
• http://www.mono-project.com/docs/getting-started/install/mac/

Or, maybe I can release directly from AppVeyor if things change (#3), and release from there? I'd need much better testing for that. And, I could update from anything, push to GitHub, and AppVeyor takes over. I'd have to expose my Chocolatey API key though, and that's not so good.

If I wanted to skip all that, the NuPkg format is just a zip file:

• http://geekswithblogs.net/TimothyK/archive/2014/03/27/creating-nuget-packages.aspx
• https://vkreynin.wordpress.com/2010/12/08/baby-steps-to-create-nuget-package/

But, then I'd need to reverse engineer the push protocol.

Test that NuSpec files do *not* have the BOM

Fix up the package icon

• Figure out what the icon should be (the Rakudo thing? Camelia?)
• Store it in this repo
• link to that in the nuspec file

The chocolatey packaging guidelines for icons: https://github.com/chocolatey/choco/wiki/CreatePackages#package-icon-guidelines

Test that PowerShell files are UTF-8 and have the BOM

• Are UTF-8
• Do not have BOM

Test that URL returns a sensible result

• The URL is https
• The URL returns something that's not an error
• The MIME type is right
• The size is about right (not something a few KB)

Deploy from AppVeyor

Push a tag and make AppVeyor push to choco. This way doesn't need my Windows virtual machines.