Robert Citek wrote:
>On Dec 20, 2005, at 5:56 PM, JT Moree wrote: > > >>AgentM wrote: >> >My only issue with cpan is that it is not really a package management >system like yum+rpm or apt+dpkg. Or is it and I'm ignorant of what >cpan can do? > >For example, with cpan how can I do the following: > >- install pre-compiled binaries of the modules. Time spent compiling >is time not spent doing something else. >- query to list the currently installed modules with versions, files, >and file locations >- uninstall a modules. This is most important when cpan fubars >something up. >- query dependencies, that is, if I remove module X what other >modules will break > >In short, can I do with cpan for perl what I can do with yum for rpms >or apt for debs? > > > In general, IMO, it is usually best to install from source, where possible. Dependency breakages occur more often with pre-compiled binaries and missing or wrong versioned libraries. With source, that is determined at config time and (usually) appropriate action is taken. CPAN.pm does a nice job of resovling dependencies and requesting installs of them. I've never had a problem with it. It does take a bit of hand-holding. Once, I had to fix a broken module before the rest of it would install. The nice feature to drop into a shell in jthe build directory was a great help. Any time spent installing from source is insignificant compared to the years of hassle free usage the app or module will give you! Ed >The other thing that kinda irks me about cpan is the docs, or rather >lack thereof. 'perldoc cpan' is a whopping 85 lines; 52 lines if you >remove the blank lines. > > > http://search.cpan.org/~andk/CPAN-1.76/lib/CPAN.pm -- Ed Howland WDT Solutions, LLC. [EMAIL PROTECTED] (314) 962-0766 _______________________________________________ CWE-LUG mailing list [email protected] http://www.cwelug.org/ http://www.cwelug.org/archives/ http://www.cwelug.org/mailinglist/
