It appears, indeed, that this line is not necessary anymore and can be safely removed altogether. I’ve just done it in the AUR package (I’m not changing pkgrel because it should not affect the generated package).
Thanks for notifying me! :)
Search Criteria
Package Details: rakudo 2024.12-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/rakudo.git (read-only, click to copy) |
---|---|
Package Base: | rakudo |
Description: | Raku compiler for MoarVM |
Upstream URL: | http://rakudo.org/ |
Licenses: | PerlArtistic |
Groups: | perl6 |
Provides: | perl6 |
Submitter: | None |
Maintainer: | hurufu |
Last Packager: | hurufu |
Votes: | 77 |
Popularity: | 0.98 |
First Submitted: | 2009-08-07 12:03 (UTC) |
Last Updated: | 2024-12-22 21:26 (UTC) |
Dependencies (2)
- nqpAUR (nqp-gitAUR, rakudo-binAUR)
- perl (perl-gitAUR) (make)
Required by (3)
- comma-ide-community (optional)
- comma-ide-complete (optional)
- zef (requires perl6)
Sources (1)
spider-mario commented on 2013-03-14 22:14 (UTC)
<deleted-account> commented on 2013-03-14 21:56 (UTC)
changing it to
mv "$pkgdir"/usr/share/man "$pkgdir"/usr/man
allowed it to compile. Not sure how to test that full functionality was retained however.
<deleted-account> commented on 2013-03-14 21:46 (UTC)
mv "$pkgdir"/usr/man "$pkgdir"/usr/share/man
breaks on me.
mv: cannot stat ‘/tmp/yaourt-tmp-skor/aur-rakudo/pkg/usr/man’: No such file or directory
This occurs after,
== Installing Binaries
...
Linked: modules/rakudo-debugger/perl6-debug
...
mv: cannot stat ‘/tmp/yaourt-tmp-skor/aur-rakudo/pkg/usr/man’: No such file or directory
an ls of /tmp/yaourt-tmp-skor/aur-rakudo/pkg/usr has lib, bin, and share. Share contains a 'man' folder not sure if that is the one that is suppose to be moved? eg. from usr/share/man to usr/man ?
spider-mario commented on 2013-01-03 15:48 (UTC)
Sorry it’s taking me so long to update the package. Due to problems when building the debugger, 2012.12 will be a non-Star package.
Fortunately, many build fixes from Rob Hoelz recently got merged upstream, so there should be no problem with 2013.01.
Pinned Comments