Update gcalcli portfile to use latest github version

[tresni (Brian Hartvigsen)]

Attached is a diff that updates the Portfile to use the lastest revision from Github. Since upstream is not using tags and I wanted to make sure people got a consistent experience, I used the revision hash and epoch to control updates. Also removed an unneeded dependancy on py27-elementtree.

[jmroot (Joshua Root)]

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?

[tresni (Brian Hartvigsen)]

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 failed to import every ics file I tried to use it with. 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/1a6fc96b03d0d137ca63bd677e677820caff0c90 .) 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.

[edit: updated to reflect that you could import files, but it just didn't work for me.]

[tresni (Brian Hartvigsen)]

Trying to work with the author to get tagged point releases. Will add a new patch file if I can make that happen.

[tresni (Brian Hartvigsen)]

Replying to 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.

[tresni (Brian Hartvigsen)]

Update Portfile to 2.4.1 release

[tresni (Brian Hartvigsen)]

Updated diff for 2.4.2 release

[dershow]

Was this ever committed? I was just trying to use gcalcli, but I can't get 'add' to work, although quick add does work. I have done a sync, and so I am using the newest version in Macports. But, it appears to be 2.1, which is fairly old. I would like to see an update, and was going to post a ticket, but then I found this first. I see that this ticket should update to 2.4.2 and make you the maintainer. But, macports still shows nomaintainer for this project.

Thanks,

--Adam

[dershow]

Cc Me!

[mf2k (Frank Schima)]

This port also needs to be updated to use the new python 1.0 portgroup. It should also support other versions of python with pythonXY variants. The default should be python27.

[mf2k (Frank Schima)]

r106091