Also note that I added generic git (git or http protocol) support a few years back. It supports arbitrary treeish targets.
The downside I found was permissions when a subsequent maintainer wants to pull. I never got sons to forcing usable permissions in the garchive directory. A second downside was needing to v drive the auto tools setup every time. There are a few examples if using this support in the tree still. Hth. Thanks -Ben On Jun 2, 2013 3:43 PM, "Peter FELECAN" <[email protected]> wrote: > "Maciej (Matchek) Bliziński" <[email protected]> writes: > > > 2013/6/2 Peter FELECAN <[email protected]>: > >> What's gathered/built depends on GITHUB_BRANCH variable, by default > >> "master"; if you provide something else, as in the example given in the > >> documentation, then that is gathered and eventually built... > > > > Aha, so it can be a sha1 sum as well, and you can do something like: > > > > GITHUB_BRANCH = d40fb7cc8f2b598df1225ec2c1841dbd6843c712 > > > > > > Then maybe the variable can be named in a fashion suggesting that you > > can put any identifier in there? > > I don't know and, consequently not tested, something like that. My > implementation is based on > http://developer.github.com/v3/repos/contents/#get-archive-link and if > what you shown is a valid Git reference the I suppose that it's > possible and if somebody test this with success we can rename it as > GITHUB_REFERENCE. > -- > Peter > _______________________________________________ > maintainers mailing list > [email protected] > https://lists.opencsw.org/mailman/listinfo/maintainers > .:: This mailing list's archive is public. ::.
_______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
