On 3/2/07, Roger Alexander <[EMAIL PROTECTED]> wrote:
> >> ...I started installing MySQL via CPAN, as I am used
> >> to doing, but when I ran into a problem installing DBD::mysql, I
> >> found and
> >> started using Fink.
> >>
> >>    So I have MySQL installed in /usr/local/mysql via CPAN.  When I
> >> run 'fink
> >> install dbd-mysql-pm588' as you suggest, it wants to install a new
> >> mysql client,
> >> among other packages, presumably under /sw.  Does that mean that
> >> Fink can't see
> >> packages outside /sw, and will it be incompatible with CPAN and
> >> manually
> >> installed packages as I keep setting things up?
> > ...
> > Fink doesn't see any packages it doesn't install itself, other than a
> > few cases where placeholders are employed.  Manually updating
> > libraries and headers in /usr/local can cause problems for Fink
> > packages.  Updating the perl modules via CPAN is likely to produce
> > unforeseen issues.
> >
> > --
> > Alexander K. Hansen
> > (akh)
> > Fink Documenter (still)
>
> I just noticed that to install DBD::mysql, not only is Fink
> installing mysql, it's installing another version of Perl!  It seems
> like overkill.  If I wanted to start clean with this new machine and
> use Fink, how deep into the pre-installed Darwin base do I need to go
> to avoid this kind of redundancy?
>
> Thanks,
>
> Roger
>

I'm not sure what you mean.

It's installing another perl because you picked the -588 version.  The
-586 variant will just use the system-installed Perl.

-- 
Alexander K. Hansen
(akh)
Fink Documenter (still)

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to