https://bugzilla.redhat.com/show_bug.cgi?id=1452985 --- Comment #12 from Paul Howarth <paul@xxxxxxxxxxxx> --- I think perl6 code in rpms should be in the vendor directories rather than the site directories. I think the precompiling of the code should happen in the rpm, as is done for python packages, but how tight a dependency on compiler version would that require? I imagine having to do a mass rebuild of all perl6 modules for minor updates of rakudo would be an onerous task if it was necessary. (In reply to Gerd Pokorra from comment #11) > I created a github repository > > https://github.com/gerd/macro.perl6.git > > with a draft for the file macros.perl6 > (https://github.com/gerd/macro.perl6/blob/master/macros.perl6) to collect > code and suggestions. I think hard-coding version numbers and directory locations is fine, particularly if the file comes with/is built from the rakudo package itself, which is where these things would be specified anyway. Everything should at least be consistent then. I think now is probably a time to brainstorm how to do perl6 packaging rather moving forward with it just yet: I'll have limited computer access next week and Petr may be busy with the Perl 5.26 mass rebuild in rawhide, though i think Jitka is running with that. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
