On Sat, Feb 23, 2013 at 3:18 PM, Jan Stary <[email protected]> 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 [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
