You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last night, I fixed a bug and used RakudoPrereq.pm6 to lock my module to latest and greatest.
I obtained the wanted version from camelia:
m: say $*PERL.compiler.version
rakudo-moar 0a1008: OUTPUT: «v2017.05.380.g.0.a.100825.d»
With the same commit built on my pristine Debian Jessie. My module failed, telling me my perl6 is not new enough.
Looking closer at the version, turns out my Debian box uses fewer chars:
Which makes the resultant Version object to be "before" the version string I got from camelia.
Commitable bot also runs on Debian jesse, but surprisingly, it gives different result from mine:
19:47 c: 0a10082 say $*PERL.compiler.version
19:47 committable6 eveo, ¦0a10082: «v2017.05.380.g.0.a.100825.d»
I first noticed this with rakudobrewed perl6, so I grabbed a checkout of Rakudo and compiled a copy manually,
yet, it still gives a different, abridged version:
There might be other cases where similar issues will occur due to strings of different lengths being used.
Would be nice to guarantee the same commit always produces the same $*PERL.compiler.version Version object.
p6rt
added
the
LTA
Less Than Awesome; typically an error message that could be better
label
Jan 5, 2020
Migrated from rt.perl.org#131539 (status was 'new')
Searchable as RT131539$
The text was updated successfully, but these errors were encountered: