Revisiting Perl
See original GitHub issueWe recently added a new version Perl. As I recently experienced while doing some testing, this going to start resulting in matrices of Perl. Am opening this issue to discuss how we want to deal with this. Do we wish to constrain the Perl versions used at conda-forge
? Should we start pinning the version? Do we just wish to tweak conda-smithy
’s lower bound on Perl?
Issue Analytics
- State:
- Created 7 years ago
- Comments:27 (17 by maintainers)
Top Results From Across the Web
Revisiting ActivePerl... Part Two! - MIDAS Blog
ActivePerl is a way of installing a Perl environment under Windows, and Perl is the underlaying programming language that our MIDAS software is ......
Read more >Revisiting Perl – George Stocker
Discovering how to build better software, together. Revisiting Perl. As I wrote in a previous blog post, I did indeed dig out my...
Read more >Revisiting Perl 6, and my first PR | Steve Bertrand [blogs.perl ...
My goal was to port my File::Edit::Portable P5 module to P6. This module saves record separators from a file, then when writing back,...
Read more >Sins of Perl Revisited
Sins of Perl Revisited · 1. Implicit Behaviors and Hidden Context Dependencies · 2. To Paren || ! To Paren? · 3. Global...
Read more >An introduction to Perl: the QuizMaker revisited - PubMed
MeSH terms. Computers; DNA Restriction Enzymes / metabolism; Databases, Factual; Human Genome Project; Humans; Information Storage and Retrieval; Internet* ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Cool. So I guess instead of trying to fix
conda-build-all
, which we would like to phase out and replace withconda-build
3, maybe it is better for us to work out whatperl
should look like in a new version ofconda-smithy
andstaged-recipes
that useconda-build
3.It appears this issue does not persist in
conda-smithy
3 RC. ( https://github.com/conda-forge/openmpi-feedstock/pull/19 ) We provide some guidance on constrainingperl
. However changing to an older version forperl
has the same outcome. IOW this issue appears to be solved in the development version ofconda-smithy
.