module precompilation should be moved to build stage

[rakudo]

module precompilation should be moved to build stage

[coke]

While I agree with the request here, should we be packaging star itself? with macports, for example, I'm trying to go the other direction - package moarvm, package nqp, then eventually package modules for installation.

[pmichaud]

I agree with "coke" -- I doubt we'll package star itself, nor will distros want us to do it that way.

Beyond that, last time I checked it's not at all trivial to build-then-install. Precompiled Rakudo modules have very tight dependencies on the compiler and libraries used in their creation. The only way to make it work reliably well is for the Rakudo binaries/libraries to be relocatable, which isn't currently possible with the Parrot backend at least.

[lizmat]

On 23 Mar 2015, at 19:27, Patrick R. Michaud [email protected] wrote:

I agree with "coke" -- I doubt we'll package star itself, nor will distros want us to do it that way.

Beyond that, last time I checked it's not at all trivial to build-then-install. Precompiled Rakudo modules have very tight dependencies on the compiler and libraries used in their creation. The only way to make it work reliably well is for the Rakudo binaries/libraries to be relocatable, which isn't currently possible with the Parrot backend at least.

But that ship has sailed, so we shouldn’t limit ourselves because of limitations on the Parrot backend.

Liz

[pstumpf]

I’ve always found rakudo-star to have a nice collection of go-to perl6 modules, so I haven’t yet bothered to integrate panda into the OpenBSD ports build system. Though if it’s the official stance that standalone rakudo is what’s supposed to be packaged by distributions, I’ll of course do that and provide separate packages for every module.

[Tyil]

I'm unsure what this issue would entail in the current iteration of Rakudo Star, so I'm closing this issue for now.