<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 27 Jan 2019, at 11:35 am, Eric F (iEFdev) <<a href="mailto:eric@iefdev.se" class="">eric@iefdev.se</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=utf-8" class="">
<div bgcolor="#FFFFFF" text="#333333" class="">
<tt class="">Hi,</tt><tt class=""><br class="">
</tt><tt class=""><br class="">
</tt><tt class="">While waiting on a PR and a ticket, I spent the weekend
looking at file I once started with.</tt><tt class=""><br class="">
</tt><tt class=""><br class="">
</tt><tt class="">// From an earlier convo (w Ryan):</tt><tt class=""><br class="">
</tt><tt class="">>>>> … since github.setup sets it for you;</tt><tt class=""><br class="">
</tt><tt class="">>>> An off-topic question about github.setup…
There's no gitlab.setup?</tt><tt class=""><br class="">
</tt><tt class="">>>> Or can it be used by manually specifying some
variables? Their API's are almost identical.</tt><tt class=""><br class="">
</tt><tt class="">>>> Haven't seen any port using Gitlab, but it
would be great if one could.</tt><tt class=""><br class="">
</tt><tt class="">>> I don't think anybody has worked on a gitlab
portgroup. I'm sure there are several ports already for software
that's hosted at gitlab. Having such a portgroup is probably a
good idea.</tt><tt class=""><br class="">
</tt><tt class="">> I started once making a version of the github-1.0.tcl.
I think I came half way, and then there was the downloads
links/API that differed a bit. I can put it up somewhere if
someone wants to help me out on it.</tt><tt class=""><br class="">
</tt><tt class=""><br class="">
</tt><tt class=""><br class="">
</tt><tt class="">So, I'd like to ask… Where to put it?</tt><tt class=""><br class=""></tt></div></div></blockquote><div><br class=""></div><div>The port group code lives in the same GitHub project as the ports. See</div><div><br class=""></div><div><a href="https://github.com/macports/macports-ports/tree/b7dbaee30cd63f197eb8d1b0db9090a5a5c948f4/_resources/port1.0/group" class="">https://github.com/macports/macports-ports/tree/b7dbaee30cd63f197eb8d1b0db9090a5a5c948f4/_resources/port1.0/group</a></div><div><br class=""></div><div>New port groups should just be added there.</div><div><br class=""></div><div>I would also say submissions of new groups should proceed as PR request just like port updates/submissions.</div><div><br class=""></div><div>Chris</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#333333" class=""><tt class="">
</tt><tt class=""><br class="">
</tt><tt class="">Since there prob are things to tweak/change (incl rm'ing my
file comments), and needs some more work, I assume it's not up for
a PR submission? Should I make a ticket of it and add my files? or
do you have some sort of “portgroup working group” that one should
send it to?</tt><tt class=""><br class="">
</tt><tt class=""><br class="">
</tt><tt class="">· Eric</tt>
</div>
</div></blockquote></div><br class=""></body></html>