#52324: syncthing @0.14.7 new port ---------------------------------+-------------------------------- Reporter: leonardo.schenkel@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: syncthing ---------------------------------+-------------------------------- More information about the project can be found at https://syncthing.net and https://github.com/syncthing/syncthing. I'm volunteering to be the maintainer of this port. As this is my first port built via Go and I'm not an expert, I'm not sure if I did it in a completely idiomatic way. Please let me know if this can be improved. I intend to introduce subports that are built from this same source for the discovery server, relay server, etc. but I want get this basic package committed first. Note that until it reaches 1.0, new versions of Syncthing (0.x) change the protocol in a non-backwards compatible way, which forces all devices to be upgrade at the same. This usually happens every few months (0.14 is from July, 0.13 from May). Because such an upgrade can be really disruptive, I would some feedback about how we handle 0.15 when it comes out: 1. should `syncthing` be upgraded to 0.15 which will break synchronization until users upgrade all their other devices? 2. should `syncthing` be upgraded to 0.15 and 0.14 becomes `syncthing-0.14`, so users can downgrade after an upgrade? (probably the port should have a note to warn users in this case) 3. should this port be named `syncthing-0.14` from the start so the user has to explicitly install `syncthing-0.15` to upgrade? (note that old versions are abandoned, they won't have security fixes — when a new version comes out we could make a new revision of the old port to tell users of that fact) 4. some other alternative that I am missing? As a user, I would probably vote for 3 to minimize any disruption of my workflow. It takes a few days/weeks for all the popular Syncthing apps (especially mobile clients) to get updated. -- Ticket URL: <https://trac.macports.org/ticket/52324> MacPorts <https://www.macports.org/> Ports system for macOS