User Details
- User Since
- Dec 13 2015, 7:56 AM (512 w, 6 d)
Yesterday
I'd argue that portclippy is wrong, don't mix GITHUB with the rest of USES section it makes harder to follow and preferably put it in a separate section below like in Porters Handbook.
https://docs.freebsd.org/en/books/porters-handbook/book/#makefile-master_sites-github
Sat, Oct 4
Sun, Sep 28
Thu, Sep 25
Sat, Sep 20
Wed, Sep 17
Aug 31 2025
You might want to add a refence?
Aug 23 2025
Aug 20 2025
Not sure if https://www.w1hkj.org/files/flrig/ is all that useful as it seems to drop legacy versions
Aug 17 2025
Aug 14 2025
Ping and you probably also want to backport, https://github.com/Thalhammer/jwt-cpp/commit/cf0dab12633bb6c39ae7a7fe147b3d2fb7b3f047
Aug 7 2025
Aug 2 2025
Aug 1 2025
Perhaps also reference upstream PR?
Jul 30 2025
Comment out this line, https://github.com/vchimishuk/loderunner-ng/blob/master/CMakeLists.txt#L24
Jul 26 2025
The interface name awg is already taken, https://cgit.freebsd.org/src/tree/sys/arm/allwinner/if_awg.c?h=releng/14.3
Jul 24 2025
Jul 21 2025
Jul 13 2025
Any attempts of upstreaming?
Jul 5 2025
Jun 29 2025
I'd value consistency over granuality that adds complexity but that's a personal opinion. If it works and Poudriere is happy I don't have any objections. Mentors?
Jun 26 2025
LGTM
Jun 25 2025
Jun 24 2025
lgtm,
While out of scope you should be able to remove GL_TAGNAME and replace PORTVERSION with DISTVERSION
To be fair I'd argue for that unless there a switch/toggle provided by upstream we always install manpages unless they have dependencies.
Yes, that should be fine in most cases.
Jun 22 2025
Either way is fine, if you want minimal impact however.... (a bit hackish) :-)