Patrick wrote regarding 'Re: [SLE] OT: Removing attachements from stored mails (or my problems with perl)' on Tue, Nov 02 at 08:30:
- Danny Sauer <suse-linux-e.suselists@danny.teleologic.net> [11-02-04 07:30]:
Carlos wrote regarding 'Re: [SLE] Removing attachements from stored mails (or my problems with perl)' on Sun, Oct 31 at 06:04: ...
So, I start downloading things from CPAN (actually, from a mirror at perl.com you mentioned). I download Email-MIME-1.8.tar.gz and try to
Ok, this is *way* easier if you use the CPAN shell. Get yourself set up as a user who can install perl modules (typically this means root), and type perl -MCPAN -e'shell' Answer the questions, and type install Email::MIME::Attachment::Stripper (for example). The cpan module will take care of installing the module and whatever modules are required. If you say "follow" rather than the default of "ask" when the CPAN setup prompts you about how to handle dependencies, you won't even have to say "yes" when it asks to download the deps. Overall the CPAN shell is super nice.
But you are going away from the SuSE distro standard rpm system and will introduce dependency problems in rpms which are false and eventually cause maintenance problems. Better to find an *rpm* solution, if possible.
Sorry - I was speaking from experience on my SuSE systems, not from pure theory. I've been using CPAN to keep my perl modules up to date since 5.x, and have had 0 problems with false dependencies related to perl modules. This is partially because almost nothing depends on perl module packages aside from other perl modules and partially because I generally run server-like machines where I'm not adding and removing random app-of-the-week all the time. I suppose that if you're a dim user who can't remember if you've installed a module or not, then you should stick with RPM for managing perl modules. Most of those users aren't gonna be using CPAN or anything like that anyway, though, since yast will take care of their deps. I'm pretty confident that "better" is in the eye of the beholder here. --Danny