On Sat, Mar 21 2020, Rafael Sadowski <[email protected]> wrote:
[...]
> Thanks Jeremie, tested with the diff qtwebkit diff below.
Thanks for testing. It's nice that you want to use the support for
"alpha" releases right now, but I wouldn't delay your qtwebkit update
for this reason.
> From /var/log/messages
> Mar 21 11:55:33 kubus pkg_add: Added qtwebkit-5.212.0p0->5.212.0-alpha4
[...]
> This diff disable dwz for now.
>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/x11/qt5/qtwebkit/Makefile,v
> retrieving revision 1.20
> diff -u -p -u -p -r1.20 Makefile
> --- Makefile 20 Mar 2020 16:44:29 -0000 1.20
> +++ Makefile 21 Mar 2020 10:56:39 -0000
> @@ -9,15 +9,13 @@ CATEGORIES = www
> DPB_PROPERTIES = parallel
>
> VERSION = ${QT5_WEBKIT_VERSION}
> -DISTNAME = qtwebkit-${QT5_WEBKIT_VERSION}-alpha3
> -PKGNAME = qtwebkit-${QT5_WEBKIT_VERSION}
> -REVISION = 0
> +DISTNAME = qtwebkit-${QT5_WEBKIT_VERSION}-alpha4
1. (pointed out by Landry earlier) the suffix should be right after the
version, ie:
DISTNAME = qtwebkit-${QT5_WEBKIT_VERSION}-alpha4
PKGNAME = qtwebkit-${QT5_WEBKIT_VERSION}alpha4
2. with explicit support for "alpha" in the pkg_* tools,
qtwebkit-5.212.0alpha4 (your update) < qtwebkit-5.212.0p0 (-current)
If you want to be benefit from support for "alpha" right now, you should
use EPOCH so that your qtwebkit update actually appears newer.
Else, you could keep using your "new alpha release -> REVISION bump"
scheme until upstream bumps to qtwebkit-5.212.1 or qtwebkit-5.213.0 etc.
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
