On May 11, 2012, at 15:07, Daniel Ericsson wrote: > On 11 maj 2012, at 21:55, Ryan Schmidt wrote: > >> On May 11, 2012, at 14:47, Daniel Ericsson wrote: >> >>> On 11 maj 2012, at 17:16, Ryan Schmidt wrote: >>> >>>> On May 11, 2012, at 10:03, Craig Treleaven wrote: >>>> >>>> We have a github portgroup which you should use. >>>> >>>> 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 >> >> Yes, there's always a redirect involved. That's fine. >> >> I just object to listing a git commit hash as if it were a version number, >> and would like a better solution than that. > > Does resetting the version number after github.setup work? Like so: > > github.setup MythTV mythtv 9ccfac11f31d8d05d48092efcbec8015c68f6cc1 > version 0.25-84 > > Or does this break stuff? This is like what I did in the py-biggles port, > when the github project name didn't match the portname.
That's one option I'm mentally considering. I don't think it breaks stuff. I'd just want to rename variables in the github portgroup to make it clear that it could be a version or a commit hash. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
