Created attachment 209516 [details]
Updated port patch
In the initial port submission, DISTVERSION was incorrectly set (rather, needed to use the date of the commit instead to avoid confusion). This is now remedied in the patch, updated to the latest commit and bumped both PORTREVISION and PORTEPOCH (plus corresponding distinfo). Also made a few minor tweaks to the Makefile for clarity.
Build info is available at https://gitlab.com/swills/freebsd-ports/pipelines/99330817
I think bumping PORTEPOCH is enough but am not really sure.
(In reply to Koichiro Iwao from comment #2)
Thanks for your response. I've been referring to the porters handbook in this particular instance, and more specifically it's noted:
> People using binary packages will never see the update if PORTREVISION is not bumped. Without increasing PORTREVISION, the package builders have no way to detect the change and thus, will not rebuild the package.
As we're changing the DISTVERSION to 'g20191028' when it was previously '0.1-1', (from what I've read) there could be a potential issue where it's not seen as an update, but rather a downgrade in version. Which lead to me bumping both of the values avoiding any conflict―forcing a rebuild of the package and prompting users of a new update.
Although I'm not 100% certain if this is completely necessary. If a change is needed I'm more than happy to do so. Cheers!
Awesome, a new tag release (v0.2) was pushed -- meaning everything I said above can be discarded. Submitting new patch now.
Created attachment 210357 [details]
* Added DISTVERSIONPREFIX and bumped DISTVERSION;
* Updated distinfo.
A commit references this bug:
Date: Wed Jan 1 21:31:38 UTC 2020
New revision: 521777
sysutils/ufetch: Update to 0.2
Submitted by: Lewis Cook <email@example.com> (maintainer)