Bug #119339 for local-lib: --no-manpages has no effect during bootstrap

Wed Dec 21 09:53:54 2016 ribasushi [...] leporine.io - Ticket created

Subject:

Bootstrapping to custom dir no longer works

Please find attached a full session of following directions as per c Note how at the end ~/perl5/ is created and referenced, despite ~/perl5-ll/ having been used earlier. It is also odd that --no-manpages had no effect, and that `perl Makefile.PL` triggered a CPAN.pm configuration + an installation of EUMM ( that was *way before* `make test` had a chance to run)

Subject:

ll_wtf.txt

Message body is not shown because it is too large.

Wed Dec 21 09:59:30 2016 ribasushi [...] leporine.io - Correspondence added

On Wed Dec 21 15:53:54 2016, RIBASUSHI wrote: Show quoted text

> Please find attached a full session of following directions as per c

Whoops that 'c' above was supposed to be: ...as per https://metacpan.org/pod/release/HAARG/local-lib-2.000019/lib/local/lib.pm#The-bootstrapping-technique

Wed Dec 21 10:21:21 2016 haarg [...] haarg.org - Correspondence added

This mostly seems to be working as expected. 1. --bootstrap has always installed CPAN/EUMM/EUI/MB immediately. It wouldn't really be possible to move it later in the process. 2. --no-manpages prevents installation of man pages by CPAN.pm for later installs. It doesn't effect the installs from the bootstrapping process, or the install of local::lib. This is also how it has always worked, but it should be fixed. 3. The local::lib directory needs to be specified when activating it. This is covered in the bootstrapping documentation ("If you passed to bootstrap a directory other than default...").

Wed Dec 21 10:21:24 2016 The RT System itself - Status changed from 'new' to 'open'

Wed Dec 21 10:27:28 2016 ribasushi [...] leporine.io - Correspondence added

On Wed Dec 21 16:21:21 2016, haarg wrote: Show quoted text

> This mostly seems to be working as expected. > > 1. --bootstrap has always installed CPAN/EUMM/EUI/MB immediately. It > wouldn't really be possible to move it later in the process.

I could swear this was not the behavior around 2012. But maybe I just misremember. Show quoted text

> 3. The local::lib directory needs to be specified when activating it. > This is covered in the bootstrapping documentation ("If you passed to > bootstrap a directory other than default...").

*ARGH* I misread this twice (I did check back before filing the bug, and missed it again). Perhaps some way to make it more prominent... maybe list one normal workflow (all steps) and one alternative workflow (all steps with the non-standard dir). Show quoted text

> 2. --no-manpages prevents installation of man pages by CPAN.pm for > later installs. It doesn't effect the installs from the bootstrapping > process, or the install of local::lib. This is also how it has always > worked, but it should be fixed.

Nod. Renaming the bug as this is the real remaining problem.

Wed Dec 21 10:28:02 2016 ribasushi [...] leporine.io - Subject changed from 'Bootstrapping to custom dir no longer works' to '--no-manpages has no effect during bootstrap'

Wed Dec 21 10:35:46 2016 haarg [...] haarg.org - Correspondence added

On Wed Dec 21 10:27:28 2016, RIBASUSHI wrote: Show quoted text

> On Wed Dec 21 16:21:21 2016, haarg wrote:

> > This mostly seems to be working as expected. > > > > 1. --bootstrap has always installed CPAN/EUMM/EUI/MB immediately. It > > wouldn't really be possible to move it later in the process.

> > I could swear this was not the behavior around 2012. But maybe I just > misremember.

Basically, EUMM has to be upgraded before it can be loaded by Makefile.PL. It would maybe be possible to do a temporary local install of EUMM, then delay the real installs until later, but that sounds like a lot of complexity for not much gain. Show quoted text

>

> > 3. The local::lib directory needs to be specified when activating it. > > This is covered in the bootstrapping documentation ("If you passed to > > bootstrap a directory other than default...").

> > *ARGH* I misread this twice (I did check back before filing the bug, > and missed it again). Perhaps some way to make it more prominent... > maybe list one normal workflow (all steps) and one alternative > workflow (all steps with the non-standard dir).

I agree that the docs could be better. I'll take a look at this.

Wed Feb 13 22:08:33 2019 hunt4reason [...] gmail.com - Correspondence added

Thats old news