[MacPorts] #24220: expat fails to activate

[MacPorts]

#24220: expat fails to activate
---------------------------------+------------------------------------------
 Reporter:  sofievalk@…          |       Owner:  ryandesign@…           
     Type:  defect               |      Status:  new                    
 Priority:  Normal               |   Milestone:                         
Component:  ports                |     Version:  1.8.2                  
 Keywords:                       |        Port:  expat                  
---------------------------------+------------------------------------------

Comment(by ryandesign@…):

 Replying to [comment:11 p.d.mosses@…]:
 > Right - but if SWI-Prolog isn't the only one, it might be helpful if
 MacPorts kept a list of those it knows about, together with hints for
 users on how to resolve port install problems due to common dependencies.

 I'm not aware of any other binary packages that install into /opt/local.
 If you find any, request their distributors pick a different prefix so
 that they don't conflict with MacPorts. Our position on this matter will
 be if you have software in /opt/local that did not come from your MacPorts
 install, you should remove it; if you cannot identify all the parts that
 got put there, uninstall all of MacPorts per the instructions in the
 Guide, then start over.

 > Presumably using -f to force a port install can break the installed SWI-
 Prolog binaries?

 Forcing activation of a port might cause problems for the standalone
 binary if the version of the port you force-activate is sufficiently
 different from the version the binary used. You should not need to be
 forcing activation. Don't use standalone binaries like SWI-Prolog's
 current binaries together with MacPorts. Pick one, and uninstall the
 other.

 > Unfortunately SWI-Prolog has been distributing those binaries for some
 time (a year or more?) and the problem with them appears only when port
 tries to install some apparently unrelated package. SWI-Prolog changing
 its prefix for new downloads doesn't help MacPorts users who have already
 installed the old ones.

 Agreed. But it's not our fault and I don't feel it's our problem. Well, it
 becomes our problem when users file tickets, but they will be closed as
 invalid with the instruction to remove everything and start over.

-- 
Ticket URL: <http://trac.macports.org/ticket/24220#comment:12>
MacPorts <http://www.macports.org/>
Ports system for Mac OS