#37153: Installing SMBup overwrites MacPorts files ------------------------+-------------------------- Reporter: cdenman@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: | ------------------------+-------------------------- Comment (by eduo@…): Hello. I feel I should add a note, should this popup in the future. Indeed, one of the ideas behind the way SMBUp installs stuff is to mimic Macports' paths so it's possible to force upgrades on it and keep SMBUp working. It installs the same dependencies as samba for macports at the time the installer was created (and warns the users it'll do so, since it actually works if Macports Samba is installed already and mentions MacPorts already exists if it's the case). It's also because all tutorials on the internet pointed to macports so by doing this paths for more advanced set-ups and tutorials still worked. So, the idea was to use the same paths as used by all tutorials out there for Samba installations on Lion and do so in a way that allowed easy recovery or updates (with --force) with macports. Newer versions (not yet released) actually change the default path and allow the user to define their own (being able to define MacPorts' but not using it any more by default), since although this was never a problem (until this thread was brought to my attention, that is) there was always the possibility of this confusion. I have had for a year a mail ready for any support question that mentions MacPorts problems indicating, precisely, how to force clean and install the various libraries. I apologize for not seeing this thread on time to comment on it. I try to keep up but somehow I missed it and didn't know about it until today (I had a mail from cdenman I sadly couldn't attend to until today). -- Ticket URL: <https://trac.macports.org/ticket/37153#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS