On 03/16/2017 05:47 PM, Olaf Alders wrote:
On Mar 16, 2017, at 5:17 PM, James E Keenan <jk...@verizon.net> wrote:
Last month I was testing the latest version of CPAN module B::C. The testing
process caused major damage to my machine. One of my FreeBSD VMs was rendered
inaccessible. All of the .xxx configuration files in my home directory
disappeared. I spent most of the next several days reinstalling the VM,
restoring my .xxx files and backing them up in an off-site repository.
I thought I was completely recovered until today. For the first time in about
6 weeks, I decide to run 'minicpan'. I typed the command by itself, as I have
always done -- and only got the usage statement. I attribute this to the
disappearance of .minicpanrc config file.
I am now running 'minicpan -l </path/to/minicpan>. AFAICT, the minicpan tree
is itself undamaged. Is there any way to simply regenerate .minicpanrc without
triggering another minicpan update process?
Hi Jim,
Could you just copy/paste it? For example, mine is currently:
local: ~/minicpan
remote: http://cpan.metacpan.org/
exact_mirror: 1
Thanks, Olaf. I guess that's the "default" .minicpanrc. But ISTR that
at one point, on xdg's suggestion, I had something that pointed to a
file whose name started with '06'.
jimk
