Change all modules.raku.org refs to raku.land

lizmat · lizmat · commit 0eac1937bfc9 · 2023-03-04T18:40:05.000+01:00
And remove some outdated references
diff --git a/doc/Language/5to6-nutshell.pod6 b/doc/Language/5to6-nutshell.pod6
@@ -33,7 +33,7 @@ original name, Perl 6, or to Perl as specifically Perl 5.>
 
 =head1 CPAN
 
-See L<https://modules.raku.org/>.
+See L<https://raku.land/>.
 
 If the module that you were using has not been converted to Raku, and
 no alternative is listed in this document, then its use under Raku may
@@ -54,15 +54,13 @@ say looks_like_number "42";    # OUTPUT: «1␤»
 
 A number of Perl modules have been ported to Raku, trying to maintain
 the API of these modules as much as possible, as part of the CPAN Butterfly
-Plan.  These can be found at L<https://modules.raku.org/t/CPAN5>.
+Plan.  These can be found at L<https://raku.land/?q=CPAN5>.
 
 Many Perl built-in functions (about a 100 so far) have been ported to
 Raku with the same semantics.  Think about the C<shift> function in Perl
 having magic shifting from C<@_> or C<@ARGV> by default, depending on context.
-These can be found at L<https://modules.raku.org/t/Perl5> as separately
-loadable modules, and in the
-L<P5built-ins|https://modules.raku.org/dist/P5built-ins> bundle to get them
-all at once.
+These can be found at L<https://raku.land/zef:lizmat/P5built-ins> and
+its dependencies.
 
 =head1 Syntax
 
diff --git a/doc/Language/5to6-perlfunc.pod6 b/doc/Language/5to6-perlfunc.pod6
diff --git a/doc/Language/5to6-perlvar.pod6 b/doc/Language/5to6-perlvar.pod6
@@ -410,8 +410,8 @@ For L<IO::CatHandle|/type/IO::CatHandle> types
 (of which L«C<$*ARGFILES>|/language/variables#index-entry-%24%2AARGFILES» is
 one), you can use L«C<on-switch>|/type/IO::CatHandle#method_on-switch» hook
 to reset line number on handle switch, and increment it manually.
-See also L«C<IO::CatHandle::AutoLines>|https://modules.raku.org/repo/IO::CatHandle::AutoLines»
-and L«C<LN>|https://modules.raku.org/repo/LN» modules that simplify this
+See also L«C<IO::CatHandle::AutoLines>|https://raku.land/zef:raku-community-modules/IO::CatHandle::AutoLines»
+and L«C<LN>|https://raku.land/zef:raku-community-modules/LN» modules that simplify this
 operation.
 
 =head3 $INPUT_RECORD_SEPARATOR, $RS, $/
diff --git a/doc/Language/about.pod6 b/doc/Language/about.pod6
@@ -38,7 +38,7 @@ To generate HTML from the Pod files, you'll need:
 which all can be installed via L<zef|https://github.com/ugexe/zef>. For
 instance, C<zef install Pod::To::HTML> to install Pod::To::HTML.
 
-=item L<C<Documentable>|https://modules.raku.org/dist/Documentable>, the
+=item L<C<Documentable>|https://raku.land/github:Raku/Documentable>, the
 document API.
 
 =item B<Optional>: L<GraphViz|https://www.graphviz.org>, for creating graphs
diff --git a/doc/Language/create-cli.pod6 b/doc/Language/create-cli.pod6
@@ -469,7 +469,7 @@ C<#|(...)> Pod block to set L«C<WHY>|/routine/WHY».
 
 You can replace or augment the default way of argument parsing by supplying a
 C<ARGS-TO-CAPTURE> subroutine yourself, or by importing one from any of
-the L<Getopt|https://modules.raku.org/search/?q=getopt> modules available
+the L<Getopt|https://raku.land/?q=getopt> modules available
 in the ecosystem.
 
 =head2 X<sub ARGS-TO-CAPTURE|Subroutines,ARGS-TO-CAPTURE>
@@ -501,7 +501,7 @@ have to reinvent the whole wheel if you don't want to.
 You can replace or augment the default way of usage message generation
 (after a failed dispatch to MAIN) by supplying a C<GENERATE-USAGE> subroutine
 yourself, or by importing one from any of the
-L<Getopt|https://modules.raku.org/search/?q=getopt> modules available in the
+L<Getopt|https://raku.land/?q=getopt> modules available in the
 ecosystem.
 
 =head2 X<sub RUN-MAIN|Subroutines,RUN-MAIN>
diff --git a/doc/Language/faq.pod6 b/doc/Language/faq.pod6
@@ -97,8 +97,8 @@ quick installation of multiple versions of Rakudo in parallel.
 
 In either case you will probably need to also install
 L«C<zef>|https://github.com/ugexe/zef» and
-L«C<rakudoc>|https://modules.raku.org/dist/rakudoc» from the
-L<ecosystem|https://modules.raku.org/>.
+L«C<rakudoc>|https://raku.land/cpan:SOFTMOTH/rakudoc» from the
+L<ecosystem|https://raku.land/>.
 
 =head2 Where can I find good documentation on Raku?
 
@@ -267,7 +267,7 @@ with L<many useful modules|https://github.com/rakudo/star/blob/master/etc/module
 Rakudo compiler-only release includes
 L<only a couple of the most basic modules|/language/modules-core>.
 
-Many more modules can be found in the L<ecosystem|https://modules.raku.org/>.
+Many more modules can be found in the L<ecosystem|https://raku.land/>.
 
 =head2 Is there something like C<B::Deparse>/How can I get hold of the AST?
 
@@ -409,7 +409,7 @@ say $foo;        # OUTPUT: «{foo => bar}␤»
 dd $foo;         # OUTPUT: «Hash $foo = ${:foo("bar")}␤»
 =end code
 
-There are also L<several ecosystem modules|https://modules.raku.org/s/dump>
+There are also L<several ecosystem modules|https://raku.land/?q=dump>
 that provide more control over how data structures are dumped, including
 support for colored output.
 
@@ -872,7 +872,7 @@ bootstrapping files created by earlier runs of the build process.
 =head2 Can I compile my script to a standalone executable?
 
 Tools like
-L«C<App::InstallerMaker::WiX>|https://modules.raku.org/dist/App::InstallerMaker::WiX»
+L«C<App::InstallerMaker::WiX>|https://raku.land/github:jnthn/App::InstallerMaker::WiX»
 allow you to create an installer that will package the compiler and your script.
 However, the currently available compilers do not support creating a standalone
 executable yet.
@@ -996,8 +996,8 @@ Fibonacci sequence, or all prime numbers.
 L<NativeCall|/language/nativecall>.
 
 =item Interfacing with Perl (CPAN) and Python modules is fairly easy with
-L<Inline::Perl5|https://modules.raku.org/dist/Inline::Perl5:cpan:NINE> and
-L<Inline::Python|https://modules.raku.org/dist/Inline::Python>
+L<Inline::Perl5|https://raku.land/cpan:NINE/Inline::Perl5> and
+L<Inline::Python|https://raku.land/cpan:NINE/Inline::Python>
 
 =item Can have multiple versions of a module installed and loaded
 simultaneously.
diff --git a/doc/Language/io-guide.pod6 b/doc/Language/io-guide.pod6
@@ -237,7 +237,7 @@ collected. To make the closing business easier, some of the methods let you
 specify a C<:close> argument, you can also use the
 L«C<will leave> trait|/language/phasers#index-entry-Phasers__will_trait», or the
 C<does auto-close> trait provided by the
-L«C<Trait::IO>|https://modules.raku.org/dist/Trait::IO» module.
+L«C<Trait::IO>|https://raku.land/zef:raku-community-modules/Trait::IO» module.
 
 =head1 The wrong way to do things
 
diff --git a/doc/Language/modules-extra.pod6 b/doc/Language/modules-extra.pod6
@@ -14,35 +14,33 @@ more fun.
 Some modules and tools to help you with generating files that are part
 of a module distribution.
 
-=item L<App::Assixt|https://modules.raku.org/dist/App::Assixt> The module developer's assistant
-=item L<App::Mi6|https://modules.raku.org/dist/App::Mi6>     Minimal authoring tool for Raku
-=item L<META6|https://modules.raku.org/dist/META6>        Do things with Raku C<META> files
-=item L<Module::Skeleton|https://bitbucket.org/rightfold/module-skeleton>        Generate a skeleton module
-=item L<rakudoc|https://modules.raku.org/dist/rakudoc>        Generate documentation end-products
+=item L<App::Mi6|https://raku.land/zef:skaji/App::Mi6>     Minimal authoring tool for Raku
+=item L<META6|https://raku.land/zef:jonathanstowe/META6>        Do things with Raku C<META> files
+=item L<rakudoc|https://raku.land/cpan:SOFTMOTH/rakudoc>        Generate documentation end-products
 
 =head1 Tests
 
 Some tests of module quality.
 
-=item L<Test::META|https://modules.raku.org/dist/Test::META>      Test your META6.json file
-=item L<Test::Output|https://modules.raku.org/dist/Test::Output>  Test the output to STDOUT and STDERR your program generates
-=item L<Test::Screen|https://modules.raku.org/dist/Proc::Screen>  Use B<GNU screen> to test full screen VT applications
-=item L<Test::When|https://modules.raku.org/dist/Test::When>  Control when your tests are run (author testing, online testing, etc.)
+=item L<Test::META|https://raku.land/zef:jonathanstowe/Test::META>      Test your META6.json file
+=item L<Test::Output|https://raku.land/github:raku-community-modules/Test::Output>  Test the output to STDOUT and STDERR your program generates
+=item L<Test::Screen|https://raku.land/github:skids/Proc::Screen>  Use B<GNU screen> to test full screen VT applications
+=item L<Test::When|https://raku.land/zef:raku-community-modules/Test::When>  Control when your tests are run (author testing, online testing, etc.)
 
 =head1 NativeCall
 
 Here some modules to help you work with NativeCall.
 
-=item L<NativeHelpers::Array|https://modules.raku.org/dist/NativeHelpers::Array>  Provides routines to deal with CArray
-=item L<App::GPTrixie|https://modules.raku.org/dist/App::GPTrixie>                Generate NativeCall code from C headers file
-=item L<NativeCall::TypeDiag|https://modules.raku.org/dist/NativeCall::TypeDiag>  Provides routines to test your CStruct
+=item L<NativeHelpers::Array|https://raku.land/zef:jonathanstowe/NativeHelpers::Array>  Provides routines to deal with CArray
+=item L<App::GPTrixie|https://raku.land/github:Skarsnik/App::GPTrixie>                Generate NativeCall code from C headers file
+=item L<NativeCall::TypeDiag|https://raku.land/github:Skarsnik/NativeCall::TypeDiag>  Provides routines to test your CStruct
 
 
 =head1 Sample modules
 
 Modules that exist only as minimalist examples, tests for installers,
 or skeletons.
 
-=item L<Foo|https://modules.raku.org/dist/Foo> A module with two distributions of different versions
+=item L<Foo|https://raku.land/github:ugexe/Foo> A module with two distributions of different versions
 
 =end pod
diff --git a/doc/Language/modules.pod6 b/doc/Language/modules.pod6
@@ -23,7 +23,7 @@ mean "module" as a set of source files in a namespace.
 
 L<C<zef>|https://github.com/ugexe/zef> is the application used for installing
 modules in Raku. Modules are listed in
-L<the Raku ecosystem|https://modules.raku.org> and can be searched there or
+L<the Raku ecosystem|https://raku.land> and can be searched there or
 from the command line using C<zef search>:
 
 =for code :lang<shell>
@@ -562,7 +562,7 @@ B<zef>, can obtain all the information needed about each C<compunit> from a
 C<META6.json> file in a directory.
 
 This also means that a testing program such as B<Perl>'s C<prove> or the B<Raku>
-equivalent L<prove6|https://modules.raku.org/dist/App::Prove6:cpan:LEONT> can be
+equivalent L<prove6|https://raku.land/cpan:LEONT/App::Prove6> can be
 run in the root directory of the B<distribution> as, e.g.,
 
 =for code :lang<shell>
@@ -658,11 +658,11 @@ Then when testing the module by the developer, use
 
 If you've written a Raku module and would like to share it with the
 community, we'd be delighted to have it listed in the
-L<Raku modules directory|https://modules.raku.org>. C<:)>
+L<Raku modules directory|https://raku.land>. C<:)>
 
 Currently, there are three ways to distribute a module. No matter which method
 you choose, your module will be indexed on the L<raku.land|https://raku.land>
-and L<modules.raku.org|https://modules.raku.org> websites. The three module
+and L<raku.land|https://raku.land> websites. The three module
 distribution networks, or ecosystems, are:
 
 =item B<zef ecosystem> using the L<C<fez> module uploader|https://raku.land/zef:tony-o/fez>
@@ -765,7 +765,7 @@ language name change.>
 =item The C<README.md> file is a
 L<markdown-formatted|https://help.github.com/articles/markdown-basics/>
 text file, which will later be automatically rendered as HTML by GitHub/GitLab for modules kept
-in those ecosystems or by L<modules.raku.org|https://modules.raku.org> website for modules
+in those ecosystems or by L<raku.lanc|https://raku.land> website for modules
 kept on L<CPAN|/language/faq#index-entry-CPAN_(FAQ)>.
 
 =item Regarding the C<LICENSE> file, if you have no other preference,
@@ -1112,9 +1112,9 @@ your module to META.list, or ping someone on IRC (#raku at libera.chat) to
 get help having it added.
 
 =item After the pull request has been accepted, wait for an hour. If
-your module doesn't show up on L<https://modules.raku.org/>, please
-view the log file at L<https://modules.raku.org/update.log> to see
-if it identifies an error with your module or C<meta> file.
+your module doesn't show up on L<https://raku.land/>, please
+view the log file to see if it identifies an error with your module or
+C<meta> file.
 
 B<That's it! Thanks for contributing to the Raku community!>
 
diff --git a/doc/Language/performance.pod6 b/doc/Language/performance.pod6
@@ -222,7 +222,7 @@ If you want to L<use Perl modules in Raku|https://stackoverflow.com/a/27206428/1
 mix in Raku types and the L<Metaobject Protocol|/language/mop>.
 
 More generally, Raku is designed to smoothly interoperate with other languages and
-there are a number of L<modules aimed at facilitating the use of libs from other langs|https://modules.raku.org/#q=inline>.
+there are a number of L<modules aimed at facilitating the use of libs from other langs|https://raku.land/?q=inline>.
 
 =head2 Make the Rakudo compiler generate faster code
 
diff --git a/doc/Language/rb-nutshell.pod6 b/doc/Language/rb-nutshell.pod6
@@ -1172,14 +1172,14 @@ command-line parsing.
 
 =head1 RubyGems, external libraries
 
-See L<https://modules.raku.org/>, where a growing number of Raku libraries
+See L<https://raku.land/>, where a growing number of Raku libraries
 are available along with the tools to manage them.
 
 If the module that you were using has not been converted to Raku, and no
 alternative is listed in this document, then its use under Raku may not
 have been addressed yet.
 
-You can experiment with L<Inline::Ruby|https://modules.raku.org/dist/Inline::Ruby:github:github:awwaiid>
+You can experiment with L<Inline::Ruby|https://raku.land/github:awwaiid/Inline::Ruby>
 to call existing Ruby code from your Raku programs. This uses an embedded
 instance of the C<ruby> interpreter to run Ruby code called from your Raku
 script. Note that this is an EXPERIMENTAL library. You can similarly call other
diff --git a/doc/Language/subscripts.pod6 b/doc/Language/subscripts.pod6
@@ -36,7 +36,7 @@ the second, and so on:
 Note that Rakudo's implementation of subscripting allows only 63 bits on
 64 bit builds. See
 L<Stack Overflow|https://stackoverflow.com/questions/61031107/do-array-indices-need-to-be-native-ints/61031617#61031617>.
-If larger subscripts are required, one may use L<Array::Sparse|https://modules.raku.org/dist/Array::Sparse>
+If larger subscripts are required, one may use L<Array::Sparse|https://raku.land/zef:lizmat/Array::Sparse>
 or alternatively, use a C<Hash> with C<Associative> subscripting (see below).
 
 =head2 B<Associative> subscripting
diff --git a/doc/Language/system.pod6 b/doc/Language/system.pod6
@@ -83,7 +83,7 @@ functions that were part of that language to modules such as
 L<C<P5getprotobyname>|https://github.com/lizmat/P5getprotobyname>, which
 includes functions such as C<endprotoent>, C<getprotoent>, C<getprotobyname>,
 C<getprotobynumber> and C<setprotoent>.
-L<Search and install C<P5> modules|https://modules.raku.org/search/?q=p5>
+L<Search and install C<P5> modules|https://raku.land/zef:lizmat/P5built-ins>
 if you want to use those functions already in Raku.
 
 =end pod
diff --git a/doc/Language/testing.pod6 b/doc/Language/testing.pod6
@@ -61,7 +61,7 @@ order and confuse the program interpreting it.
 
 There are no current plans to make it thread safe. If threaded-testing is
 crucial to you, you may find some suitable
-L<ecosystem modules|https://modules.raku.org/search/?q=Test> to use
+L<ecosystem modules|https://raku.land/?q=Test> to use
 instead of C<Test> for your testing needs.
 
 =head1 Running tests
@@ -73,7 +73,7 @@ command line:
 $ raku t/test-filename.rakutest
 
 To run all tests in the directory recursively,
-L<prove6|https://modules.raku.org/dist/App::Prove6> application can
+L<prove6|https://raku.land/cpan:LEONT/App::Prove6> application can
 be used.
 
 You have to install it before using with zef:
@@ -92,7 +92,7 @@ distribution path, it is an equivalent of C<-Ilib> argument of
 C<raku> command.
 
 For more documentation regarding C<prove6> usage refer to
-L<its page|https://modules.raku.org/dist/App::Prove6>.
+L<its page|https://raku.land/cpan:LEONT/App::Prove6>.
 
 To abort the test suite upon first failure, set the
 C<RAKU_TEST_DIE_ON_FAIL> environmental variable:
diff --git a/doc/Programs/01-debugging.pod6 b/doc/Programs/01-debugging.pod6
@@ -95,21 +95,21 @@ their documentation.
 
 Historically other modules have existed and others are likely to be
 written in the future. Please check the L<Raku
-Modules|https://modules.raku.org/> website for more modules like these.
+Modules|https://raku.land/> website for more modules like these.
 
-=head2 L<C<Debugger::UI::CommandLine>|https://modules.raku.org/repo/Debugger::UI::CommandLine>
+=head2 L<C<Debugger::UI::CommandLine>|https://raku.land/github:jnthn/Debugger::UI::CommandLine>
 
 A command-line debugger frontend for Rakudo. This module installs the
 C<raku-debug-m> command-line utility, and is bundled with the Rakudo
 Star distributions. Please check
 L<its repository|https://github.com/jnthn/rakudo-debugger>
 for instructions and a tutorial.
 
-=head2 L<C<Grammar::Debugger>|https://modules.raku.org/repo/Grammar::Debugger> (and C<Grammar::Tracer> in the same distribution)
+=head2 L<C<Grammar::Debugger>|https://raku.land/github:jnthn/Grammar::Debugger> (and C<Grammar::Tracer> in the same distribution)
 
 Simple tracing and debugging support for Raku grammars.
 
-=head2 L<C<Trait::Traced>|https://modules.raku.org/repo/Trait::Traced>
+=head2 L<C<Trait::Traced>|https://raku.land/cpan:KAIEPI/Trait::Traced>
 
 This provides the C<is traced> trait, which automatically traces usage of
 features of whatever the trait is applied to. What features of whatever the
diff --git a/doc/Type/IO/Path.pod6 b/doc/Type/IO/Path.pod6
@@ -477,7 +477,7 @@ L<Seq|/type/Seq> before doing something like recursively performing more C<dir>
 calls. You can exhaust it by assigning to a C<@->sigiled variable or simply
 looping over it. Note how examples below push further dirs to look through into
 an L<Array|/type/Array>, rather than immediately calling C<dir> on them. See
-also L«C<IO::Dir> module|https://modules.raku.org/dist/IO::Dir» that gives you
+also L«C<IO::Dir> module|https://raku.land/zef:raku-community-modules/IO::Dir» that gives you
 finer control over closing dir handles.
 
 Examples:
diff --git a/doc/Type/independent-routines.pod6 b/doc/Type/independent-routines.pod6
@@ -101,7 +101,7 @@ this to work correctly.
 
 More languages may be supported with additional
 modules which may be found from the
-L<Raku Modules Directory|https://modules.raku.org/search/?q=inline>.
+L<Raku Modules Directory|https://raku.land/?q=inline>.
 
 If the optional  C<$filename> parameter is given, the
 L«C<$?FILE>|/language/variables#index-entry-$%3FFILE» variable is set to
