On Fri, 24 Jan 2003, Randal L. Schwartz wrote: > >>>>> "Hisashi" == Hisashi T Fujinaka <[EMAIL PROTECTED]> writes: > > Hisashi> The reason I quit using cpan is because it puts things places I don't want > Hisashi> (overwriting /usr/bin/head, for example) > > No longer. And it put stuff there only because that's where you told > it to put Perl. I build into /opt for everything, and have never had > a problem.
I told perl nothing. Apple told perl to put things there, apparently. Because of Apple, using CPAN directly is dangerous. > Hisashi> and I never knew you could update > Hisashi> in cpan. There's probably configuration I don't know about. > > Hisashi> Updating in perl is much easier and most of the perl-modules should be > Hisashi> up-to-date since some stinker (me) emails the maintainers every time their > Hisashi> modules are updated. > > The rest of the suggestions in this thread are welcome, but I still > think we need to consider that fink is likely to be used by > power-compilers like me as well as naive compilers that simply want > access to cool Unix binaries for OSX. > > What's the next step? Well, you never told me how to automatically update things using CPAN. Because of that, I still find CPAN to be of marginal use and much harder to use than the fink perl modules. My personal opinion is to use fink, and let the CPAN users figure things out on their own. -- Hisashi T Fujinaka - [EMAIL PROTECTED] BSEE (6/86) + BSChem (3/95) + BAEnglish (8/95) + $2.50 = mocha latte ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
