<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#333333">
<br>
<div class="moz-cite-prefix">On 1/16/19 23:11 , Ryan Schmidt wrote:<br>
</div>
<blockquote
cite="mid:FBA674B2-E52A-47BD-8E5B-251FAD56158F@macports.org"
type="cite">
<blockquote type="cite">
<pre wrap="">For the maintainer… The old 'libgeoip' was pixilla. I sent him an email asking if he wanted this one as well, but haven't heard anything. I guess nomaintainer is better, unless I should be in there. It's ok.
</pre>
</blockquote>
<pre wrap="">pixilla hasn't been seen in awhile. We're planning to remove him as maintainer:
<a class="moz-txt-link-freetext" href="https://trac.macports.org/ticket/57827">https://trac.macports.org/ticket/57827</a>
If you want to maintain the port (submit updates; have tickets about the port assigned to you) then list yourself, otherwise don't.
</pre>
</blockquote>
Ok, yes you can add me there, like you wrote earlier.<br>
<br>
<br>
<blockquote
cite="mid:FBA674B2-E52A-47BD-8E5B-251FAD56158F@macports.org"
type="cite">
<pre wrap="">If you can do everything that needs to be done for the destroot phase in Tcl code in the Portfile, then yes, you could override the destroot phase entirely using a destroot block.
</pre>
</blockquote>
I sitting with your Portfile edition (mod_*) now and adding the
rest. A 'notes', etc. But, it doesn't <strike>install</strike> go
in to destroot. Only if I use destroot {}. I'll make a post in the
ticket about it.<br>
<br>
I thought maybe the other Makefile(.am) should get the same edits,
but it didn't work.<br>
<br>
<blockquote type="cite">Ok, if you'd like to make further changes in
your branch and submit a PR, that's fine. Or if you'd like to
attach updated Portfiles to the Trac tickets that's fine too.
</blockquote>
<blockquote
cite="mid:FBA674B2-E52A-47BD-8E5B-251FAD56158F@macports.org"
type="cite">
<pre wrap="">If you have further questions about how to do something in a Portfile, asking on the mailing list is fine. If you have updated versions of Portfiles or patches, attaching them to the ticket is good, or put them in your branch and send a link to that.
</pre>
</blockquote>
Ok. Perfect!<br>
<br>
<br>
<blockquote
cite="mid:FBA674B2-E52A-47BD-8E5B-251FAD56158F@macports.org"
type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">… since github.setup sets it for you;
</pre>
</blockquote>
<pre wrap="">An off-topic question about github.setup… There's no gitlab.setup?
Or can it be used by manually specifying some variables? Their API's are almost identical.
Haven't seen any port using Gitlab, but it would be great if one could.
</pre>
</blockquote>
<pre wrap="">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.</pre>
</blockquote>
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.<br>
<br>
<br>
· Eric<br>
</body>
</html>