@@ -15,15 +15,16 @@ but it should be pretty straight forward to setup a development environment and
15
15
## Requirements
16
16
17
17
* a git client (should be compiled with libpcre)
18
- * perl 5.22 or later (5.22 is the recommended version, consider [ using perlbrew] ( https://perlbrew.pl ) )
18
+ * perl 5.36 or later (5.36 is the recommended version, consider [ using perlbrew] ( https://perlbrew.pl ) )
19
19
* App::cpanminus (read manual on [ metacpan] ( https://metacpan.org/pod/App::cpanminus ) )
20
20
21
21
### git with pcre support
22
22
23
23
For macOS users, it's recommended to use [ homebrew] ( https://brew.sh ) to install git with pcre support
24
24
25
25
> brew install pcre
26
- > brew reinstall --with-pcre git
26
+ > export USE_LIBPCRE=yes
27
+ > brew reinstall --build-from-source git
27
28
28
29
You can check if git support pcre by using the '-P' option
29
30
@@ -32,7 +33,7 @@ You can check if git support pcre by using the '-P' option
32
33
33
34
## Cloning repositories
34
35
35
- You should start forking the main ( metacpan-grep-front-end repository) [ https://github.com/metacpan/metacpan-grep-front-end ]
36
+ You should start forking the main [ metacpan-grep-front-end repository] ( https://github.com/metacpan/metacpan-grep-front-end )
36
37
You can then clone it locally (where you should replace ~ YOUR-GITHUB-USERNAME~ by your github username )
37
38
38
39
> git clone [email protected] :~YOUR-GITHUB-USERNAME~/metacpan-grep-front-end.git
@@ -41,14 +42,14 @@ You can then clone it locally (where you should replace ~YOUR-GITHUB-USERNAME~ b
41
42
42
43
The frontend is not using a database, but a ` git repo ` itself as a backend.
43
44
For this the production is using one huge git repository (~ 20 Go) indexing all the CPAN in one place !
44
- You can read more on this topic and find tools used to build this Git repo on the ( GitHub Repos) [ https://grep.metacpan.org/source-code ] page.
45
+ You can read more on this topic and find tools used to build this Git repo on the [ GitHub Repos] ( https://grep.metacpan.org/source-code ) page.
45
46
46
47
We do not want to use such a beast during development cycles, we only need a smaller version of it,
47
- you can simply clone it from this ( metacpan-cpan-extracted-lite) [ https://github.com/metacpan/metacpan-cpan-extracted-lite ] .
48
+ you can simply clone it from this [ metacpan-cpan-extracted-lite] ( https://github.com/metacpan/metacpan-cpan-extracted-lite ) .
48
49
It should be clone at the same level of * metacpan-grep-front-end* itself (do not clone it inside the repository).
49
50
50
51
# clone at the same level of metacpan-grep-front-end
51
- # cd ..; # if you are in metacpan-grep-front-end repo
52
+ # cd .. # if you are in metacpan-grep-front-end repo
52
53
> git clone https://github.com/metacpan/metacpan-cpan-extracted-lite.git
53
54
54
55
# you should have something like this
@@ -59,7 +60,7 @@ It should be clone at the same level of *metacpan-grep-front-end* itself (do not
59
60
60
61
Now that you have the repository set, let's install all the perl modules required.
61
62
62
- You can check your perl version. ( 5.022001 is the recommended one for now )
63
+ You can check your perl version. ( 5.036000 is the recommended one for now )
63
64
64
65
perl -E 'say $]'
65
66
@@ -120,7 +121,7 @@ From there you should be ready to
120
121
121
122
The project comes with a basic ` .travis.yml ` file.
122
123
123
- If you want to start smoking your own branches, you simply need to link your [ GitHub account] ( https://github.com )
124
- to your ( Travis CI account) [ https://travis-ci.org/ ] , then enable the repository in your ( Travis Dashboard) [ https://travis-ci.org/dashboard ]
124
+ If you want to start smoking your own branches, you simply need to link your [ GitHub account] ( https://github.com/ )
125
+ to your [ Travis CI account] ( https://travis-ci.org/ ) , then enable the repository in your [ Travis Dashboard] ( https://travis-ci.org/dashboard )
125
126
126
127
Note that any Pull Request submitted via GitHub would trigger a Travis smoke without any settings required from your side :-)
0 commit comments