<div dir="ltr">> It's way over the top for this 75 year old programmer, so please disregard.<div><br></div><div>P. S. I will take a look at the thing and let you know.</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Jun 19, 2025 at 3:24 AM Sergey Fedorov <<a href="mailto:vital.had@gmail.com">vital.had@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div>Looking at the FreeBSD port, it appears that writing a portfile should be trivial: <a href="https://github.com/freebsd/freebsd-ports/blob/26c9ff20a25d7529b2ef609ffece11cd1bbeb879/x11/hamclock/Makefile" target="_blank">https://github.com/freebsd/freebsd-ports/blob/26c9ff20a25d7529b2ef609ffece11cd1bbeb879/x11/hamclock/Makefile</a><div>(I have no idea whether it will build without manual fix-ups to the code, but at least it should not be needed to handle multiple targets manually.)</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 19, 2025 at 3:14 AM Elwood Downey <<a href="mailto:elwood.downey@gmail.com" target="_blank">elwood.downey@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Dave,<div><br></div><div>Many thanks for jumping in. You are generous and brave.</div><div><br></div><div>I tried again to study <a href="https://guide.macports.org/chunked/development.html" target="_blank">https://guide.macports.org/chunked/development.html</a> but I gotta say I quickly glazed over with all the stuff about phases and overrides and config.args and variants and on and on ... nine chapters worth! HamClock has some 40 different make targets so I can't begin to imagine how all these would get handled.</div><div><br></div><div>It's way over the top for this 75 year old programmer, so please disregard.</div><div><br></div><div>All the best to everyone, long live macports!</div><div><br></div><div>Elwood</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 18, 2025 at 10:22 AM Dave Allured - NOAA Affiliate <<a href="mailto:dave.allured@noaa.gov" target="_blank">dave.allured@noaa.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>I will be glad to submit a pull request for HamClock, if you would kindly complete a few things. Perhaps someone more generous than me, would like to spend time on this; but I would like you to complete basic portfile debugging, so that I do not have to do it.</div><div><br></div><div>1. Add minimal dependency instructions. You say "X11 libs", but X11 is more fine-grained than that. This depends on which specific X11 functions and headers are referenced in your code. Do not over-link to libraries that your code does not use. See other X11-based ports for examples. I believe that you get the X11 server automatically, so nothing to do there.</div><div><br></div><div>2. Add minimal portfile instructions to satisfy the basic configure, build, and install phases. MacPorts does some of this by default for standard make-based builds, so there may be little or nothing to do.</div><div><br></div><div>3. Prepare a *complete* portfile to minimum MacPorts guidelines. Your sample is lacking the initial format line, and I don't know what else. It will suffice if your portfile can simply pass `port lint --nitpick` with no errors or warnings.</div><div><br></div><div>4. Test on your own MacPorts installation. When it installs and tests correctly, send the portfile, plus version ID's for your macOS, Xcode, and Command Line Tools.</div><div><br></div><div>5. I would prefer if you would open a Trac ticket for this new port request. Post results and any questions on that ticket. If you do not want to create a Trac login, then just post results and questions to this thread.</div><br><a href="http://guide.macports.org/#project" target="_blank">http://guide.macports.org/#project</a></div><div dir="ltr"><br></div><div dir="ltr"><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 17, 2025 at 10:21 PM Elwood Downey <<a href="mailto:elwood.downey@gmail.com" target="_blank">elwood.downey@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello!<div><br></div><div>Although I have been a happy user of macports since, I dunno, 2010 maybe (whenever Panther or Leopard came out), I've never submitted a port myself. And I eschew that <i>brew</i> thing so that was never an option for me.</div><div><br></div><div>I skimmed your instructions for submitting a new port but 1) I do not have and do not want a github account and 2) I am super lazy when it comes to systemy things, I only enjoy programming.</div><div><br></div><div>So on the outside chance someone else would be willing to do it all for me, I hereby humbly submit my amateur radio program <a href="https://clearskyinstitute.com/ham/HamClock" target="_blank">HamClock</a> for consideration as a new port.</div><div><br></div><div>I grabbed an example Portfile and filled in a few fields, the result is pasted below. The only dependencies are Xcode command line tools and Xquartz for X11 libs and an X server, nothing else. Otherwise it's an ordinary g++ program built with <i>make</i> and installed with the usual <i>sudo make install</i>. Should be very easy :-)</div><div><br></div><div>I don't want to be the maintainer either (!) but the program doesn't really need one because it's entirely self-updating. Anyone installing an ancient version via macports will be able to upgrade to the latest with just two clicks within the program itself. The version on macports can stay the same forever.</div><div><br></div><div>My purpose in writing is that there are now about 10,000 HamClock users on all manner of UNIX-like systems but only about 10 on macOS. I am just hoping that providing a macports starting point for folks might bump that fraction up a bit.</div><div><br></div><div>Well, there it is. If I'm way off base here, I understand completely and apologize for taking your time.</div><div><br></div><div>Cheers, and thanks for reading,</div><div><br></div><div>Elwood Downey</div><div>Tucson AZ</div><div><br></div><div><br></div><div><font face="monospace">name hamclock<br>version 4.18<br>categories amateur radio<br>platforms darwin<br>license MIT<br>maintainers Elwood Downey, <a href="mailto:ecdowney@clearskyinstitute.com" target="_blank">ecdowney@clearskyinstitute.com</a><br>description provides useful data for amateur radio operators<br>long_description HamClock is a kiosk-style application that provides real time space weather, radio propagation models, operating events and other information particularly useful to the radio amateur.<br>homepage <a href="https://www.clearskyinstitute.com/ham/HamClock" target="_blank">https://www.clearskyinstitute.com/ham/HamClock</a><br>master_sites <a href="https://www.clearskyinstitute.com/ham/HamClock/ESPHamClock.tgz" target="_blank">https://www.clearskyinstitute.com/ham/HamClock/ESPHamClock.tgz</a></font></div></div>
</blockquote></div></div>
</div>
</blockquote></div>
</blockquote></div>
</blockquote></div>