Comment 1 Charlie Li 2024-11-22 20:04:59 UTC

Comment on attachment 255376 [details]
[PATCH] comms/chirp: update 20240910 → g20241119

Not adding a g to DISTVERSION; the program itself expects a numeric-only datestamp as version, as it matters for its internal update checking (not that we really care, but still). I will handle this.

Comment 2 Älven 2025-02-05 22:34:31 UTC

Created attachment 257279 [details]
[PATCH] comms/chirp: update 20240910 -> 20250205

Comment 3 Charlie Li 2025-02-05 22:58:02 UTC

Comment on attachment 257279 [details]
[PATCH] comms/chirp: update 20240910 -> 20250205

RUN_DEPENDS are sorted the way they are to stay consistent with upstream, even if out of alphabetical order. There was no need to un-silence any commands currently silenced. portscout already doesn't operate on this port because there are no formal releases apart from datestamps.

Most importantly, I still need to do further runtime testing, there are some things in that department not quite accounted for. Also with PEP-517 stuff.

Comment 4 Diane Bruce 2025-04-14 12:55:31 UTC

This is a hamradio@ port and it appears ready for commit.

Comment 5 Charlie Li 2025-04-14 15:43:49 UTC

(In reply to Diane Bruce from comment #4)
Already been outdated, have a copy from this month being dogfooded.

Comment 6 Diane Bruce 2025-04-14 18:32:01 UTC

(In reply to Charlie Li from comment #5)
Excellent! I just didn't want this to get forgotten and I also can use the program. :)

Comment 7 Älven 2025-08-08 14:40:38 UTC

Created attachment 262801 [details]
[PATCH] comms/chirp: Update 20240910 => 20250806

Comment 8 Charlie Li 2025-08-18 21:06:46 UTC

I have not finished testing the latest few commits yet. One nagging fit-and-finish issue stems from what the about dialog shows the version as, which lately has been "py3dev". This is more fine if the program was packaged directly from the source distribution, but Dan's (upstream) "binary" snapshots show the snapshot date string. May or may not have some implications.

Also, note that for every commit to this port I've made, the GH_TAGNAME is from a pull request, that is rebased every time, to convert the build to PEP-517. Generally, USE_PYTHON=distutils (ie direct setup.py execution) has been deprecated ever since but now the clock is ticking for `setup.py install`.

Comment 9 Yuri Victorovich 2025-11-10 07:01:58 UTC

Approved.


Thanks,
Yuri

Comment 10 commit-hook 2025-11-10 20:08:28 UTC

A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=19c04024e8750381e047e38c5c7b5fa78ac169d7

commit 19c04024e8750381e047e38c5c7b5fa78ac169d7
Author:     Älven <alven@FreeBSD.org>
AuthorDate: 2025-08-08 14:37:27 +0000
Commit:     Älven <alven@FreeBSD.org>
CommitDate: 2025-11-10 20:08:00 +0000

    comms/chirp: Update 20240910 => 20251106

    + Add WWW for source code repository
    * Pet portclippy(1) and portfmt(1)
    * Use distutils for now, as with pep517 it fails at stage phase,
      while upstream don't have any plans on implementing it either.

      https://github.com/kk7ds/chirp/pull/609#pullrequestreview-1435569432

    PR:             282904
    Approved by:    hamradio@ (alven@, yuri@)
    Approved by:    yuri@ (Mentor)

 comms/chirp/Makefile  | 22 ++++++++++------------
 comms/chirp/distinfo  |  6 +++---
 comms/chirp/pkg-plist |  1 +
 3 files changed, 14 insertions(+), 15 deletions(-)