Update Clementine Player to the top of the github tree as we haven't seen an actual release for years.

[sbruno]

Summary

Start tracking nightly releases of audio/clementine

[tcberner]

audio/clementine-player/Makefile

41

^ how about using the tag name as version -- the bump alone does not give the users any information on what there version actually is.
See Example 14 in the chapter 5 [1]

[1] https://docs.freebsd.org/en/books/porters-handbook/makefiles/

[sbruno]

Address pkg naming convention.

[sbruno]

audio/clementine-player/Makefile

41

So, I tried the above DIST variables which generates a pkg name of: clementine-player-1.4.0.r1.586

This does *not* seem to supercede the previous pkg name of 1.4.0_6 which is irritating. Any suggestions on how to proceed?

[tcberner]

Note, that you will require to set PORTEPOCH as

pkg version -t clementine-player-1.4.0_6 clementine-player-1.4.0.r1.586
>

[sbruno]

In D30029#674233, @tcberner wrote:

Note, that you will require to set PORTEPOCH as

pkg version -t clementine-player-1.4.0_6 clementine-player-1.4.0.r1.586
>

That will work for this update. But, until the actual verson number (1.4.0) is updated, I have to leave the PORTEPOCH value in there, right? Else users updating from the current release to any future release will fail?

[sbruno]

• Add a PORTEPOCH for this change so that users actually see a valid update

[tcberner]

In D30029#674771, @sbruno wrote:

In D30029#674233, @tcberner wrote:

Note, that you will require to set PORTEPOCH as

pkg version -t clementine-player-1.4.0_6 clementine-player-1.4.0.r1.586
>

That will work for this update. But, until the actual verson number (1.4.0) is updated, I have to leave the PORTEPOCH value in there, right? Else users updating from the current release to any future release will fail?

The PORTEPOCH will have to stay for ever (or until the pkgname changes).