#14172: unison upgrade removed unison-2.13 - synchronization with some machines fails ----------------------------------+----------------------------------------- Reporter: vinc17@macports.org | Owner: eridius@macports.org Type: defect | Status: reopened Priority: High | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: ----------------------------------+----------------------------------------- Changes (by vinc17@macports.org): * priority: Normal => High * status: closed => reopened * resolution: invalid => Comment: Replying to [comment:3 eridius@macports.org]:
Don't you think that would be confusing for new users?
No. And if you fear that would confuse new user, unison-2.13 could depend on unison (though this isn't a real dependency), so that users could choose the version they want/need.
If you weren't willing to upgrade on all machines, why did you upgrade at all?
Because MacPorts asked me to upgrade. Moreover there could be new features and new bug fixes. But I still need unison 2.13 for machines I can't upgrade (e.g. I'm not the admin, they are Debian/stable machines and so on).
Not installing {{{${prefix}/bin/unison}}} wouldn't work anyway, as uninstalling the previous version would remove it.
Users who need unison-2.13 would not uninstall this port! ${prefix}/bin/unison is useless since there is ${prefix}/bin/unison-2.13. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14172#comment:4> MacPorts </projects/macports> Ports system for Mac OS