Changes between Version 95 and Version 96 of ProblemHotlist

Timestamp:

Dec 5, 2012, 9:24:32 PM (12 years ago)

Author:

ryandesign (Ryan Carsten Schmidt)

Comment:

add SMBup to list of software that installs files on top of MacPorts ports

ProblemHotlist

@@ -163 +163 @@
 xmlwf is a part of the expat port (which is a dependency of many other ports, and thus is likely to be one of the first ports to ever get installed), but for some reason this file already exists on your computer, and MacPorts did not install it.
 
-One possible reason for this is that you have installed a 3rd-party software package -- possibly [http://gprolog.univ-paris1.fr/#download gprolog] or [http://www.swi-prolog.org/download/stable swi-prolog] -- which was itself built with MacPorts, set to its default prefix, and therefore conflicts with your normal use of MacPorts in its default prefix. The developers of the 3rd-party package you installed should not have distributed their software in this manner; they should have configured MacPorts in a custom prefix instead, one that is unique to their software. (For example, in the case of swi-prolog, /usr/local/swi-prolog or /opt/swi-prolog would be good choices.)
+One possible reason for this is that you have installed a 3rd-party software package—possibly [http://gprolog.univ-paris1.fr/#download gprolog] or [http://www.swi-prolog.org/download/stable swi-prolog] or [http://eduo.info/apps/smbup SMBup]—which was itself built with MacPorts, set to its default prefix, and therefore conflicts with your normal use of MacPorts in its default prefix. The developers of the 3rd-party package you installed should not have distributed their software in this manner; they should have configured MacPorts in a custom prefix instead, one that is unique to their software. (For example, in the case of swi-prolog, /usr/local/swi-prolog or /opt/swi-prolog would be good choices.)
 
 Another possible reason is that you previously had MacPorts (and expat and probably other ports) installed, then somehow uninstalled MacPorts itself, or at least its registry of which ports are installed, without actually uninstalling those ports, and have now installed MacPorts again with a clean registry, which therefore thinks no ports are installed, though some still are.