#37302: Update gcalcli portfile to use latest github version -----------------------------+-------------------------------- Reporter: brian.andrew@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: gcalcli | -----------------------------+-------------------------------- Changes (by ryandesign@…): * keywords: => haspatch -- Ticket URL: <https://trac.macports.org/ticket/37302#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#37302: Update gcalcli portfile to use latest github version -----------------------------+-------------------------------- Reporter: brian.andrew@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: gcalcli | -----------------------------+-------------------------------- Comment (by brian.andrew@…): The last "stable" (2.1) release is 15 months old and didn't properly function for my Google Apps instances, had issues with anything that forced SSL (even with https parameter set), and lacks support for importing ics files. The current development snapshot has been in the repository for 5 months and there is no indication of an impending point based release (other then the update to the version at https://github.com/insanum/gcalcli/commit/1a6fc96b03d0d137ca63bd677e677820ca... .) The author asked on a reported issue why people don't just use the data in git (https://github.com/insanum/gcalcli/issues/29), made a vague comment that may indicate willingness to tag a point release, but no tag has actually been made. That was a month ago. I figured other people may be interested in a port that actually worked so hence my patch. Not sure what you meant by "You can override the values set by the portgroup." I saw no need to override any of the values, using epoch seemed to be the appropriate method for controlling whether an updated was needed. If a point release is a must, it would be fairly trivial to fork the project and tag a release myself, but I thought it best to leave everything pointed at the original author's repository. -- Ticket URL: <https://trac.macports.org/ticket/37302#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#37302: Update gcalcli portfile to use latest github version -----------------------------+-------------------------------- Reporter: brian.andrew@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: gcalcli | -----------------------------+-------------------------------- Comment (by brian.andrew@…): Replying to [comment:2 jmr@…]:

Don't use the commit hash as the version, use a version that monotonically increases. Preferably one that will still do so if/when a new release is tagged. You can override the values set by the portgroup.

For that matter, is there a compelling reason to update to a development snapshot? Or has upstream said that there will not be any more stable releases?

I've updated the port file to use the latest point releases. I am now a committer on the project and have been working with the author to make sure to tag releases as appropriate. This will (likely) be the last release in the 2.0 line as we switch the new Google Data APIs. That is all happening in the master branch on Github right now, but we don't have an ETA on the first 3.0-line release. Let me know if there is anything else I can do to assist in getting this change committed. -- Ticket URL: <https://trac.macports.org/ticket/37302#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS

#37302: Update gcalcli portfile to use latest github version -----------------------------+-------------------------------- Reporter: brian.andrew@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: gcalcli | -----------------------------+-------------------------------- Comment (by macsforever2000@…): This port also needs to be updated to use the new python 1.0 portgroup. -- Ticket URL: <https://trac.macports.org/ticket/37302#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X