Broken perl configuration

[Brandon Allbery]

On Sat, Feb 23, 2013 at 3:18 PM, Jan Stary <hans at stare.cz> wrote:

> Why would macports even care about something
> 'not installed by a portfile' (which I read:
> not installed via macports)?


MacPorts doesn't.  Which is in some sense the problem:  MacPorts can't
protect you from some port inappropriately finding your manually installed
program and using it, and then breaking because it didn't get updated after
you upgraded some dependency.  If it was installed from a Portfile, then
MacPorts can at least try to use that Portfile to rebuild it (e.g. some XS).

Actually, there is one case where MacPorts cares:  you install something
manually, later you install something via MacPorts that wants to write
files in the same place.  It will abort in that case rather than
overwriting your files, preventing your install.

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130223/01c4455e/attachment.html>