#35639: Unison 2.32 port ---------------------------------+------------------------------------------ Reporter: rwilcox@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: unison, unison232, unison240 ---------------------------------+------------------------------------------ Comment(by rwilcox@…): Replying to [comment:3 ryandesign@…]:
Replying to [comment:2 rwilcox@…]:
The new unison232 and unison240 ports must have their install locations changed so that they do not conflict with one another.
I'm curious what would happen if you had two unison versions installed at the same time. For example, are there any changes to the settings and/or various archive formats that makes having two versions of Unison simultaneously installed a Really Bad Idea.
That's a good question. We could further modify each version of unison to give each its own settings file / config area, or whatever it is that unison has.
Let me go do some research and ask on the Unison mailing list and see what they say :)
My thought was just that if the client and server versions must match, then who's to say a user wouldn't have one server they need to communicate with that uses one version, and a different server that uses a different version? Thus they would need to have both versions of the client software on their computer installed at the same time.
It's a good question - I've been avoiding that issue by punting (activating / deactivating the proper port)... but maybe it's a problem that needs to be solved. And maybe it makes sense to copy the route taken by python_select (??) -- Ticket URL: <https://trac.macports.org/ticket/35639#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS