-
Notifications
You must be signed in to change notification settings - Fork 19
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
Specify a minimum version requirement #58
Comments
This requirement should help avoid old language versions trying to run code written in a more recent language version and thus also avoid unnecessary build errors on e.g. Travis etc. See Raku#58 as well as Raku/examples#53 for more details.
This requirement should help avoid old language versions trying to run code written in a more recent language version and thus also avoid unnecessary build errors on e.g. Travis etc. See Raku#58 as well as Raku/examples#53 for more details.
After looking at the Travis conf, it doesn't seem to be relevant to do any version checks there since everything comes from the docker image. Or would you like the docker image to start and then the Travis config to check the available Raku version in there? Somehow that solution feels complicated. @JJ what do you think? |
Actually, there are docker images for most versions. Additionally, there are GitHub actions for different OSs. So maybe Gh actions is the way to go. Check what I just did for Pod-to-cached should you need an example |
Do you mean this commit: perl6/Pod-To-Cached@58a2752 ? |
Do you propose that the Travis config explicitly use e.g. the 6.d version? The current version uses |
Correct, that's the one. |
raku-test always contains the latest released version. And you are right, that one does not have tags; alpine-raku does. I will see if there's a good way of creating derived containers with tags |
Would it make sense to extend the list of docker images available in Raku/docker? That way one could point to community-maintained images. |
It might, but I'm not totally sure who's actually uploading them to Docker hub. Again, it would make sense to create a GitHub Action that uploaded them automatically to Github registry... |
I'm checking if there's some automated way to create Docker images with tags out of tagged base images, and yep, there is. However, it involves scripting the build process. I haven't done it so far. Again, probably easier with GitHub Docker Registry. |
Check out Raku/examples#53 for an explanation. Use either 6.d or 2018.11, whatever is the most suitable. Add also version checks in the Travis conf.
The text was updated successfully, but these errors were encountered: