in reply to telling users how to get CPAN modules
For instance, I got an e-mail today from a Linux user (he didn't specify what distribution) who tried running the installer script, and had a problem because he'd never installed CPAN.pm.Uhm, really? CPAN.pm comes with perl.
It's nice that CPAN is cross-platform, but getting CPAN set up in the first place is nontrivial for many users. (The number of configuration questions it asks is just astounding, and it's not necessarily true that you can give the default answer to every single one.)Well, if the defaults would always work, there wouldn't be a reason to ask the questions, would there? The number of configuration questions is astouding, because there is an astouding number of ways things could be set up at the user.
My software is open-source, so I have no way of knowing what percentage of users are actually having problems, but I'd like to make it easier for them.Easier than CPAN or CPANPLUS? If you find a way (that is, a way that doesn't comprimise by not working in cases where CPAN or CPANPLUS works), please to feed your results back into CPAN/CPANPLUS.
I use FreeBSD myself, and it's not practical for me to create and test separate versions for every Linux distribution.Yup. And it's unpractical for thousands of other maintainers as well. That's why we have CPAN and CPANPLUS. That's why it's smart to set up your installation that it makes use of CPAN or CPANPLUS (and guess what will happen if you start with h2xs?)
Abigail
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: telling users how to get CPAN modules
by biosysadmin (Deacon) on Mar 21, 2004 at 17:05 UTC |