> The user does not know where they installs things. > Packaged installers, the users just click through.
> The user is typically unaware of where packaged software is installed. You > can look at our mounds of trouble tickets that were caused by this specific > reason. > The user simply ran some installer program, and magic happened. > > And how do we stop the user from rewriting something that is already there? > > We don't, and we can't. It's the user's responsibility to not be an idiot > > and rewrite something he has installed himself before. > > That is a reason why we shouldn't use /usr/local: users are less to ran an > installer that clobbers inside MacPorts-specific directories. > There is a huge difference between: > * the user explicitly running a command to overwrite MacPorts, and > * the user ran an installer that did something somewhere. > > When the user runs an installer program, chances are it won't install to > /opt/local but instead install to /usr/local or /Library. > Since /usr/local is a prime target, it would be very likely that users > routinely overwrite MacPorts on accident. OK. This convinces me that /usr/local would not be good. Thank you for your time. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
