submitting a new port, sort of

[Dave Allured - NOAA Affiliate]

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.

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.

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.

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.

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.

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.

http://guide.macports.org/#project


On Tue, Jun 17, 2025 at 10:21 PM Elwood Downey <elwood.downey at gmail.com>
wrote:

> Hello!
>
> 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 *brew* thing so that was never an option for me.
>
> 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.
>
> So on the outside chance someone else would be willing to do it all for
> me, I hereby humbly submit my amateur radio program HamClock
> <https://clearskyinstitute.com/ham/HamClock> for consideration as a new
> port.
>
> 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 *make* and installed with the usual *sudo
> make install*. Should be very easy :-)
>
> 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.
>
> 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.
>
> Well, there it is. If I'm way off base here, I understand completely and
> apologize for taking your time.
>
> Cheers, and thanks for reading,
>
> Elwood Downey
> Tucson AZ
>
>
> name                hamclock
> version             4.18
> categories          amateur radio
> platforms           darwin
> license             MIT
> maintainers         Elwood Downey, ecdowney at clearskyinstitute.com
> description         provides useful data for amateur radio operators
> 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.
> homepage            https://www.clearskyinstitute.com/ham/HamClock
> master_sites
> https://www.clearskyinstitute.com/ham/HamClock/ESPHamClock.tgz
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20250618/3ffe908d/attachment.htm>