Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Feb 2016 15:33:57 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 206840] x11-fm/doublecmd: Update to 0.7R6569, Fix build
Message-ID:  <bug-206840-13-o1G9hs0ZuW@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206840-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-206840-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206840

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needs-patch

--- Comment #3 from Kubilay Kocak <koobs@FreeBSD.org> ---
(In reply to Be=C3=B1at Gonzalez Etxepare from comment #2)

You're welcome Be=C3=B1at

Basically DISTVERSION can be used to convert incompatible version strings i=
nto
PORTVERSION compatible ones. That is to say, setting DISTVERSION
*automatically* calculates a PORTVERSION value.

See Table 5.2 in
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.ht=
ml

In this case,

DISTVERSION=3D0.7R6569 make -V PORTVERSION

results in:

PORTVERSION =3D 0.7.r6569

Testing this value:

pkg version -t 0.7.r6569 0.7.0
<

^--- good (0.7.r6569 is less than future 0.7.0 (true))

Whereas:

pkg version -t 0.7R6569 0.7.0
>

^--- not good (0.7R6569 is greater than future 0.7.0 (false))

So you see why we need to use DISTVERSION, otherwise PORTEPOCH will be need=
ed
in the future.

Since we'll be setting DISTVERSION, you may also need to override DISTFILES=
 in
order to derive the correct distribution file filename.

Hope that helps explain things :)

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206840-13-o1G9hs0ZuW>