Skip Menu |

This queue is for tickets about the CPANPLUS CPAN distribution.

Report information
The Basics
Id: 17009
Status: resolved
Priority: 0/
Queue: CPANPLUS

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

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



Subject: Configuration not in the /etc directory
Other modules with global configurations put them in a location inside of etc, such as /etc/perl/Module/Name.pm . CPANPLUS mixes it's "config file" into the main shared libs as a module. CPANPLUS should (by default) install it's config.pm into /etc and not the libs dir.
From: MTHURN [...] cpan.org
I disagree. By its very nature, CPANPLUS's configuration is NOT global, it is tied to the perl it was installed with; if you have more than one perl installed, you need more than one CPANPLUS configuration. In addition, a NON-global configuration allows individual users WITHOUT root permissions to use CPANPLUS to maintain their own private collections of modules. These are huge benefits which IMO completely outweigh any possible benefits of a global/root configuration. -- - - Martin 'Kingpin' Thurn
On Wed Jan 11 09:00:07 2006, MTHURN wrote: Show quoted text
> I disagree. By its very nature, CPANPLUS's configuration is NOT > global, it is tied to the perl it was installed with; if you have > more than one perl installed, you need more than one CPANPLUS > configuration. In addition, a NON-global configuration allows > individual users WITHOUT root permissions to use CPANPLUS to > maintain their own private collections of modules. These are huge > benefits which IMO completely outweigh any possible benefits of a > global/root configuration.
I quite agree with this. Also, as a practical limitation: /etc is a debian policy decision. Freebsd would use /usr/local/etc/ and so it continues between many flavours of distributions. Aside from the fact that not every distribution has a policy at all (where would it go on VMS or win32 or cygwin?), and that EU::MM doesn't appear to have an install directive that uses the 'correct' policy, the directory the file would end up in, wouldn't be in your perl include path either. It seems that the specific downsides of this approach outweigh the benefits. Luckily, most vendors will alter packages to suit their specific policies, so the debian package for CPANPLUS should do exactly what you as a debian user would expect. -- Jos