Skip Menu |

This queue is for tickets about the Module-Install CPAN distribution.

Report information
The Basics
Id: 43195
Status: rejected
Priority: 0/
Queue: Module-Install

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

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



Subject: Module::AutoInstall -- must not attempt to auto-install without a terminal
We're building quite a number of CPAN modules in PLD Linux; the build process executes without a terminal. As per this report: https://bugs.launchpad.net/pld-linux/+bug/327917 Module::AutoInstall puts CPAN into an infinite loop, eventually filling the disk with the STDOUT/STDERR log file. Besides, nothing is supposed to be installed via CPAN.pm on the build machines. It should behave as if --skipdeps was provided if either of these is true: a) there is no attached terminal b) is being run under RPM (detectable eg. by the presence of $ENV{RPM_BUILD_ROOT})
Hi. There's no simple and portable terminal detection. So I don't think Module::Install should try to find a terminal to change its behavior. And I don't think we should take special care for RPM either. You can set, for example, PERL_MM_USE_DEFAULT environment variable to skip prompts (not only those of Module::Install, but other decent tools). You also might want to upgrade CPAN.pm to use its distroprefs system to help your building system. Closed this ticket as "wontfix". Thanks. On 2009-2-11 Wed 04:23:44, RADEK wrote: Show quoted text
> We're building quite a number of CPAN modules in PLD Linux; the build > process executes without a terminal. As per this report: > > https://bugs.launchpad.net/pld-linux/+bug/327917 > > Module::AutoInstall puts CPAN into an infinite loop, eventually
filling Show quoted text
> the disk with the STDOUT/STDERR log file. Besides, nothing is
supposed Show quoted text
> to be installed via CPAN.pm on the build machines. > > It should behave as if --skipdeps was provided if either of these is
true: Show quoted text
> > a) there is no attached terminal > b) is being run under RPM (detectable eg. by the presence > of $ENV{RPM_BUILD_ROOT})