Skip Menu |
 

This queue is for tickets about the CPAN CPAN distribution.

Report information
The Basics
Id: 52520
Status: open
Priority: 0/
Queue: CPAN

People
Owner: Nobody in particular
Requestors: mschwern [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 1.9402
Fixed in: (no value)



Subject: $module->get chdirs to the build directory
Download (untitled) / with headers
text/plain 328b
While writing some CPAN automation tools I discovered that $module->get was chdir'ing to the CPAN build directory but not back out. This makes developing using CPAN::Shell difficult as you're never quite sure what directory you'll wind up in. Ideally the user visible routines of CPAN should not result in a changed directory.
Subject: Re: [rt.cpan.org #52520] $module->get chdirs to the build directory
Date: Sun, 6 Dec 2009 22:56:30 -0500
To: bug-CPAN [...] rt.cpan.org
From: David Golden <dagolden [...] cpan.org>
Download (untitled) / with headers
text/plain 700b
On Sun, Dec 6, 2009 at 10:39 PM, Michael G Schwern via RT <bug-CPAN@rt.cpan.org> wrote: Show quoted text
> While writing some CPAN automation tools I discovered that $module->get > was chdir'ing to the CPAN build directory but not back out.  This makes > developing using CPAN::Shell difficult as you're never quite sure what > directory you'll wind up in. > > Ideally the user visible routines of CPAN should not result in a changed > directory.
The "problem" is that "get" is really "get and decide which PL file to use". Worse, that's where configure_requires get satisfied. Sometime "soonish", I'd like to refactor all PL selection and configuration out of get() and make() into a separate routine. -- David


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.