Fetching tarball of a commit

[Craig Treleaven]

At 9:47 PM +0200 5/11/12, Daniel Ericsson wrote:
>On 11 maj 2012, at 17:16, Ryan Schmidt wrote:
>  > On May 11, 2012, at 10:03, Craig Treleaven wrote:
>  >> So, I'm back working on a port of MythTV; thanks to Michael 
>Dickens for finding and fixing a flaw in the QT4-mac port.  I really 
>want to use a recent version of the Fixes/0.25 branch as some bugs 
>affecting the Mac were fixed recently.  A Myth dev tells me that 
>GitHub deliver the identical zipball for a particular commit (say 
>9ccfac11f3...) via:
>>>
>>> 
>>>https://github.com/MythTV/mythtv/zipball/9ccfac11f31d8d05d48092efcbec8015c68f6cc1
>  >> [snip]
>  > We should improve the github portgroup so that it can fetch 
>tarballs from arbitrary revisions. Currently it only fetches 
>tarballs for tags.
>
>I do this in some local Portfiles, checking it now it's seems to get 
>redirected, but it works.
>
>PortSystem          1.0
>PortGroup           github 1.0
>
>checksums           rmd160  38cf5c7de055057df1fc081d261e198d45127f3d \
>                     sha256 
>c866214e6c54731a8cf6a89b7c85b3c631db22db1228db63403ccf7aabca38cc
>
>github.setup MythTV mythtv 9ccfac11f31d8d05d48092efcbec8015c68f6cc1

Daniel:

Thank you very much!  That works perfectly.  BTW, it also works with 
the short hash as well, ala ...

github.setup		MythTV mythtv 9ccfac11f3

To me, if one is pulling a specific Git commit, the version should 
include the date.  Eg:

version             0.25-fixes-20120510

This way, when you update the port to a new commit, just update the 
date at the same time.  Unless, of course, you plan to update 
multiple times per day!  ;)

Craig