Raku programmers have come to expect a specific collection of modules from the Raku ecosystem be installed with the Rakudo compiler by default.[1] This collection is known as the "Star Bundle." While there is an all-in-one source tarball[2] to build Rakudo Star, this probably isn't in keeping with the Gentoo way of building software. There is a script that ships with Rakudo[3] that should allow ebuild maintainers to build Raku modules individually and reproduce the Star bundle. There is however one gotcha, I believe that all Raku modules would have to be rebuilt whenever Rakudo is updated. I think portage already has hooks for that kind of thing, but I'm hazy on the details. [^1] https://github.com/rakudo/star/blob/master/etc/modules.txt [^2] https://rakudo.org/star [^3] https://github.com/rakudo/rakudo/blob/master/tools/install-dist.p6 Reproducible: Always
`dev-lang/rakudo:=` should rebuild raku modules whenever rakudo is updated?
(In reply to crocket from comment #1) > `dev-lang/rakudo:=` should rebuild raku modules whenever rakudo is updated? I pinged the author of the zef package manager in the #raku (Libra.chat) IRC channel and we had the following exchange: > <jgaz> question: assuming a manually compiled install, should modules be rebuilt every time rakudo is upgraded? > > <ugexe> jgaz: they [Raku modules] will be recompiled when you upgrade > <ugexe> not rebuilt (i.e. running a Build.rakumod file) So, it seems the answer to your question is "no." This does not appear to be a requirement.
(In reply to crocket from comment #1) > `dev-lang/rakudo:=` should rebuild raku modules whenever rakudo is updated? Elizabeth Mattijsen also commented about this on IRC in the same channel: > <lizmat> jgaz: yes, they will be automatically rebuilt whenever you try to load it [a Raku module]
