Skip to content

Commit 8ef15ef

Browse files
author
Tadeusz Sośnierz
committed
Fix a few things
1 parent 26c1b4a commit 8ef15ef

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

misc/perl6advent-2010/articles/module-system.pod

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
=head1 Writing the Perl 6 modules
1+
=head1 The Perl 6 module ecosystem
22

33
The Perl 6 module database on L<http://modules.perl6.org> is certainly
44
not CPAN yet, but there are still a number of things worth using, or
@@ -22,9 +22,8 @@ live on github currently).
2222
That will download neutro and bootstrap it using the supplied libs.
2323
What we end up is the module installer itself, and the File::Tools and
2424
Module::Tools distributions. From now on, assuming C<~/.perl6/bin> is in
25-
your PATH and C<~/.perl6/lib> is in your PERL6LIB (check your
26-
C<~/.profile> or C<~/.bashrc> to be sure), you will be able to install
27-
modules as simply as with cpanminus:
25+
your PATH (check your C<~/.profile> or C<~/.bashrc> to be sure), you
26+
will be able to install modules as simply as with cpanminus:
2827

2928
neutro json
3029
neutro perl6-Term-ANSIColor
@@ -38,14 +37,12 @@ list:
3837
neutro update # fetch the fresh list of modules
3938
neutro list
4039

41-
Modules will be installed to C<~/.perl6/lib> as well, so assuming your
42-
PERL6LIB is alredy set, you are now able to use the installed modules:
40+
Modules will be installed to C<~/.perl6/lib>, which is in the default
41+
search path of Rakudo, so you don't really need to set PERL6LIB yourself:
4342

4443
perl6 -e 'use Term::ANSIColor; say colored("Hello blue world!", "blue")'
4544

46-
=head2 The module ecosystem
47-
48-
You probably just can't wait to write your first module and make it
45+
and C<~/.perl6/lib> is in your PERL6LIB You probably just can't wait to write your first module and make it
4946
available for the whole world. There's no CPAN where you can send your
5047
packages; the usual workflow is creating a repository on L<Github|http://github.com> and adding it to the L<projects.list|https://github.com/perl6/ecosystem/blob/master/projects.list>
5148
file in the L<ecosystem|https://github.com/perl6/ecosystem>. You don't
@@ -55,3 +52,4 @@ send a patch, or just ask some of the commiters or people on the #perl6
5552
channel of Freenode.
5653

5754
TBD: Link to module writing guide, anything else?
55+
TODO for tadzik: remove the PERL6LIB warning in neutro

0 commit comments

Comments
 (0)