Skip Menu |
 

This queue is for tickets about the CPAN CPAN distribution.

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

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

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: How do you do an 'o conf commit' when running 'cpan -i Module::Foo'
Download (untitled) / with headers
text/plain 664b
I upgraded CPAN to 1.8801 from the version shipped with Perl 5.8.8 on a server and ran into an interesting scenario later. My next run with CPAN was to run 'cpan -i Catalyst::Devel' (the module is probably irrelevant). Upon starting CPAN ran me through a few various configuration steps for the new version. At the end, it mentioned that to save the changes, I needed to issue an 'o conf commit'. The problem is that with running a 'cpan -i', I'll never see an interactive line to type the 'o conf commit' into. So, next time I run CPAN, I'll have to reconfigure again, or, as is the case with Catalyst::Devel, even during the install of the current module.
Download (untitled) / with headers
text/plain 397b
My idea is the auto_commit variable implemented in 1.88_68 which I just uploaded. I made it mandatory that every user configures this variable, so even users coming via the cpan script will have a chance to force immediate write-to-disk behaviour. Either a 1.8803 is called for or 1.89 comes soon enough... Don't know yet. I leave this ticket open and welcome further opinions on this. Thanks,


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.