#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: ---------------------------------+------------------------------------------ Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: Thanks. You've named this new port unison32, but since the version of this port is 2.32.52 it seems best to name the port unison232. Does that sound ok to you? Since this situation of needing the same version of unison on the client and server seems destined to continue, we should replace the existing unison port with a unison240 port, and in future add new ports if new versions of unison are released. The version of unison240 should be 2.40.63, since that is the stable version, not 2.40.65, since according to #35116 that one is not stable and does not work right. The new unison232 and unison240 ports must have their install locations changed so that they do not conflict with one another. The existing unison port can be kept as a stub port marked as replaced_by unison240 to facilitate upgrades. The whitespace of the existing unison port (and this unison232 port) does not conform to the modeline. I'd like to make an initial commit to fix the whitespace to conform to our guidelines. Then we can copy it to make the new ports. You indicated you'd like to maintain this new unison232 port. Would you like to maintain the new unison240 port and the unison stub port as well? Since you are not a committer it would make things easier if we would make the ports openmaintainer as well, so that we would not need to ask your approval before making minor changes such as version updates. Let me know if that's ok with you. There are some probably unintended differences between this new unison232 port and the existing unison port, such as the missing license line and the missing description of the aqua variant. The livecheck of the new unison232 and unison240 ports should be changed to only find stable versions of those respective branches, or turned off if no new releases of that branch are expected. I will investigate whether it might be simpler to implement the unison232 and unison240 ports as subports of the unison port; this would eliminate the need to manually keep separate portfiles synchronized. I can work on these various issues tomorrow, if you have no objections, and I'll attach new Portfiles here for your contemplation. -- Ticket URL: <https://trac.macports.org/ticket/35639#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS