Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 89 lines (71 sloc) 4.273 kb
fe29cde @coke README should be in text, not POD.
coke authored
1 Rakudo Perl 6
2 This is Rakudo Perl, a Perl 6 compiler for the Parrot virtual machine.
1b6cbf6 @pmichaud First draft of a perl 6 parser in p6 rules and pir.
pmichaud authored
3
b2e9a57 @pmichaud Update README.
pmichaud authored
4 Rakudo Perl is Copyright (C) 2008-2011, The Perl Foundation. Rakudo Perl
fe29cde @coke README should be in text, not POD.
coke authored
5 is distributed under the terms of the Artistic License 2.0. For more
6 details, see the full text of the license in the file LICENSE.
1b6cbf6 @pmichaud First draft of a perl 6 parser in p6 rules and pir.
pmichaud authored
7
19931fe @pmichaud Update README with pointer to Rakudo Star distributions.
pmichaud authored
8 This directory contains only the Rakudo Perl 6 compiler itself; it
9 does not contain any of the modules, documentation, or other items
10 that would normally come with a full Perl 6 distribution. If you're
11 after more than just the bare compiler, please download the latest
12 Rakudo Star package from http://github.com/rakudo/star/downloads .
ec2f831 @Daenyth README: Added section about Rakudo packages, and a link to the Arch Linu...
Daenyth authored
13
cbdfa61 @moritz [README] add pointer to status page
moritz authored
14 For a high-level overview of implemented and missing features,
15 please visit http://perl6.org/compilers/features .
16
90f996e @moritz move most of the build instructions into a separate INSTALL file
moritz authored
17 Building Rakudo
b4a3407 @pmichaud Typo reported by diakopter++: "prerequisits" -> "prerequisites".
pmichaud authored
18 See the INSTALL.txt file for detailed prerequisites and build and
90f996e @moritz move most of the build instructions into a separate INSTALL file
moritz authored
19 installation instructions. The short version is
20
652952a @colomon Add --gen-nqp to the Configure instructions.
colomon authored
21 $ perl Configure.pl --gen-parrot --gen-nqp
90f996e @moritz move most of the build instructions into a separate INSTALL file
moritz authored
22 $ make
23 $ make spectest # optional
24 $ make install # IMPORTANT, installs to install/bin/perl6
25
26 Note that the 'make install' step is necessary for running
27 Rakudo from outside the build directory. But don't worry, it
28 installs locally by default, so you don't need any administrator
29 privileges for carrying out this step.
fe29cde @coke README should be in text, not POD.
coke authored
30
31 Where to get help or answers to questions
32 There are several mailing lists, IRC channels, and wikis available with
33 help for Perl 6 and Rakudo on Parrot. Figuring out the right one to use
34 is often the biggest battle. Here are some rough guidelines:
35
b2e9a57 @pmichaud Update README.
pmichaud authored
36 The central hub for Perl 6 information is http://perl6.org/ .
37 This is always a good starting point.
38
fe29cde @coke README should be in text, not POD.
coke authored
39 If you have a question about Perl 6 syntax or the right way to approach
40 a problem using Perl 6, you probably want the "perl6-users@perl.org"
b2e9a57 @pmichaud Update README.
pmichaud authored
41 mailing list or the "irc.freenode.net/#perl6" channel. The perl6-users
42 list is primarily for the people who want to use Perl 6 to write
43 programs, so newbie questions are welcomed there. Newbie questions
44 are also welcome on the #perl6 channel; the Rakudo and Perl 6
45 development teams tend to hang out there and are generally glad
46 to help. You can follow "@rakudoperl" on Twitter, and there's
47 a Perl 6 news aggregator at <http://planetsix.perl.org> .
48
49 Questions about NQP can also be posted to the #perl6 IRC channel.
50 For questions about Parrot, see <http://parrot.org/> for links and
51 resources, or join the #parrot IRC channel on irc.perl.org .
fe29cde @coke README should be in text, not POD.
coke authored
52
53 Reporting bugs
54 Bug reports should be sent to "rakudobug@perl.org" with the moniker
55 [BUG] (including the brackets) at the start of the subject so that it
56 gets appropriately tagged in the RT system (https://rt.perl.org/rt3/).
57 Please include or attach any sample source code that exhibits the bug,
58 and include either the release name/date or the git commit identifier.
59 You find that information in the output from "perl6 --version" (or in
60 the first line of "git log", if Rakudo fails to build). There's no need
61 to cc: the perl6-compiler mailing list, as the RT system will handle
62 this on its own.
63
64 Submitting patches
65 If you have a patch that fixes a bug or adds a new feature, please
66 submit it to "rakudobug@perl.org" with the moniker [PATCH] (including
67 the brackets) at the start of the subject line. We'll generally accept
68 patches in any form if we can get them to work, but unified diff from
69 the "git" command is greatly preferred. In general this means that in
70 the "rakudo" directory you make your changes, and then type
71
72 git commit -m 'Your commit message' changed/filename.pm
73 git format-patch HEAD^
74
75 This will generate a file called "001-your-commit-message.patch", or
76 more of them if you made multiple commits; please attach these to your
77 email.
78
b2e9a57 @pmichaud Update README.
pmichaud authored
79 (Note to the maintainers: you can apply these patches with the
80 "git-am -s" command; it preserves meta information like author).
fe29cde @coke README should be in text, not POD.
coke authored
81
82 How the compiler works
83 See docs/compiler_overview.pod.
84
85 AUTHOR
b2e9a57 @pmichaud Update README.
pmichaud authored
86 Patrick Michaud "pmichaud@pobox.com" is the current pumpking for
87 Rakudo Perl 6. See CREDITS for the many people that have contributed
88 to the development of the Rakudo compiler.
Something went wrong with that request. Please try again.