I play in a different playground and primarily use either master, dev or develop branches as I run with latest codebase available. ffmpeg, imagemagick, opencv, clang6, openblas, etc. These get a lot of PRs everyday.
Having to update the Portfiles manually with latest hash and date/version is not optimal. Why can't a script find the repo, verify hash and date automatically then archive or if you have a GitHub account verify your SSH, and just grab the repo without creating an archive. > On Mar 7, 2018, at 02:32, Enrico Maria Crisostomo > <enrico.m.crisost...@gmail.com> wrote: > > This is a little bit offtopic IMHO, anyway: I found surprising too that the > github portgroup was not documented, given the high percentage of software > that I build out of github repositories, and that's why I recently > contributed the documentation of the github portgroup: > > https://github.com/macports/macports-guide/pull/12 > > It has been merged some days ago. Yet, I don't see it online yet. > >> On 7 Mar 2018, at 11:29, db <iams...@gmail.com> wrote: >> >>> On 7 Mar 2018, at 01:53, Rainer Müller <rai...@macports.org> wrote: >>>> On 2018-03-06 23:00, db wrote: >>>> [...] an *overview* of how to write a portfile is much needed. >>> Isn't this what this chapter in the guide is supposed to provide? >>> https://guide.macports.org/#development >> >> Yes, supposed. When you're in it's difficult to say, but AFAIR I was >> probably trying to write a portfile for something hosted on GitHub without >> knowing about the relative portgroup and its documentation being buried >> somewhere under the prefix in the tcl file itself. >
