Package Details: rakudo-star 2017.07-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.478042
First Submitted: 2010-08-06 13:18
Last Updated: 2017-08-02 14:47

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

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:

dietchrst commented on 2017-01-12 19:06

the source listed here is wrong for the current package. I have to manually download the sources, and the rakudo-star-2015.06.tar.gz is behind the current one (2016.12). It was easy to get the correct one, but might be confusing.

savagezen commented on 2016-12-13 16:30

Thanks @blippy. You're correct. Update has been pushed.

blippy commented on 2016-12-13 12:51

I think your checksum is wrong:
sha512sum rakudo-star-2016.11.tar.gz
77803d3e5e81c89d7a9ebbd6405c4675e58560a8feff555b3dd8a142d4460ad0f18c005e385788344f75efe79be4368a75d81f6aa346bd53792513c7775c99bd rakudo-star-2016.11.tar.gz

All comments