Package Details: rakudo-star 2018.10-2

Git Clone URL: (read-only)
Package Base: rakudo-star
Description: Rakudo Perl6 on MoarVM with additional modules
Upstream URL:
Licenses: PerlArtistic
Conflicts: rakudo-moarvm, rakudo-star
Provides: rakudo-moarvm, rakudo-star
Submitter: maleadt
Maintainer: savagezen
Last Packager: savagezen
Votes: 15
Popularity: 0.000097
First Submitted: 2010-08-06 13:18
Last Updated: 2018-11-12 02:00

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

1 2 3 Next › Last »

savagezen commented on 2017-11-05 18:53

As discussed below, I have created a metapackage to install the Rakudo Star modules if Zef has already been installed. Zef is the Perl6 module manager and requires Rakudo (Perl6) to have already been installed.

savagezen commented on 2017-10-29 20:21


Thanks for the feedback. The short answer is "no" I haven't got this to build / work properly. You're correct about a meta-package being the way to go. I've been holding out hope that each new release would fix DESTDIR support, but it hasn't.

I can set to work on the meta-package, but haven't had much time lately. If you (or anyone) are inclined to do so, you'll also need to make a 'zef' package to that will be used to install the Star modules on top of rakudo. That said, you'll also want to use the *-git versions of moarvm, nqp, and rakudo as another ongoing issue has been that the official releases of those packages are "not new enough" to support the Star modules.

piojo commented on 2017-10-29 04:26

This package isn't building, and the "star" modules aren't even designed to build unless rakudo is already installed. It fails as soon as zef starts to compile, because it looks for /usr/share/perl6/runtime/perl6.moarvm, but the file only exists as $pkgdir/usr/share/perl6/runtime/perl6.moarvm.

Since this isn't even supposed to work--upstream said it would make more sense for "star" or "star-packages" to be a meta package which ONLY includes modules, and will be built after rakudo is installed.

(stmuk is the rakudo-star maintainer, so that is as official as it gets.)

So it actually makes sense to remove this package and replace it with a "star-modules" package.

atweiden commented on 2017-08-07 02:18

Could you install tools/ to /usr/bin, e.g.

install -Dm 755 tools/ "$pkgdir/usr/bin/perl6-install-dist"

This makes it possible to install perl6 pkgbuilds system-wide without downloading the script per package.

savagezen commented on 2017-06-25 19:05


I'm not sure of the issue, however I'm looking into it. There is a forum thread created by someone else to discuss.

newnumbertwo commented on 2017-06-20 05:53

Does not build. Ends with:

== Installing modules for MoarVM
cd modules/zef && sh -c "PATH=/usr/bin:/home/USERNAME/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl /tmp/yaourt-tmp-USERNAME/aur-rakudo-star/pkg/rakudo-star/usr/bin/perl6-m -Ilib bin/zef install ."
Unhandled exception: While looking for '/usr/share/perl6/runtime/perl6.moarvm': no such file or directory
make: *** [Makefile:66: modules-install-m] Error 1
==> ERROR: A failure occurred in package().
==> ERROR: Makepkg was unable to build rakudo-star.
==> Restart building rakudo-star ? [y/N]
==> ------------------------------------

savagezen commented on 2017-01-20 00:03

Thanks @spider-mario. Update had been pushed.

spider-mario commented on 2017-01-18 09:06

The difference with the contents of the PKGBUILD is due to the fact that the .SRCINFO is out of date (and that’s where the AUR gets its version number from). You can regenerate it using mksrcinfo.

dietchrst commented on 2017-01-13 03:24

Yes that makes sense - that PKGBUILD will pull the current one. I was facing a proxy issue, which was avoided by just manually downloading the sources myself and then building from there. It isn't something I normally do, and that's what made me notice the difference in what is listed by the AUR as the source. I don't maintain packages, so I don't really know how it works, or how common it is that there is a difference between what's listed and what the PKGBUILD says. Thanks for responding so quick, and thanks for keeping this current!

savagezen commented on 2017-01-12 20:05

@dietchrst The PKGBUILD is correct. It will build the 2016.11 upstream release (which is the current one, not 2016.12).

The AUR is reporting the version (and corresponding "Sources") as 2015.06 and I'm not sure what is causing that. If you've got suggestions for that, you can make an issue or pull request on GitHub: