<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>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. </div><div><br></div><div>Having to update the Portfiles manually with latest hash and date/version is not optimal. </div><div><br></div><div>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.</div><div><br>On Mar 7, 2018, at 02:32, Enrico Maria Crisostomo <<a href="mailto:enrico.m.crisostomo@gmail.com">enrico.m.crisostomo@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8">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:<div class=""><br class=""></div><div class=""><a href="https://github.com/macports/macports-guide/pull/12" class="">https://github.com/macports/macports-guide/pull/12</a></div><div class=""><br class=""></div><div class="">It has been merged some days ago. Yet, I don't see it online yet.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 7 Mar 2018, at 11:29, db <<a href="mailto:iamsudo@gmail.com" class="">iamsudo@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 7 Mar 2018, at 01:53, Rainer Müller <<a href="mailto:raimue@macports.org" class="">raimue@macports.org</a>> wrote:<br class=""><blockquote type="cite" class="">On 2018-03-06 23:00, db wrote:<br class=""><blockquote type="cite" class="">[...] an *overview* of how to write a portfile is much needed.<br class=""></blockquote>Isn't this what this chapter in the guide is supposed to provide?<br class=""><a href="https://guide.macports.org/#development" class="">https://guide.macports.org/#development</a><br class=""></blockquote><br class="">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.</div></div></blockquote></div><br class=""></div></div></blockquote></body></html>