svn commit: r349818 - head/www/nginx

[Mathieu Arnold]

+--On 9 avril 2014 06:09:26 +0000 Alexey Dokuchaev <danfe at FreeBSD.org>
wrote:
| [*] Your mentor should have also mentioned that PORTEPOCH bumps should be
| generally avoided, as it can never go back (well, there is a way to hack
| around it, but it requires renaming the package, which makes it even more
| ugly and discouraged).

Well, no, it is *not* what a mentor should say.  PORTREVISION and PORTEPOCH
should be set when they need to be, they should not be avoided because
someone think they're ugly.  Like the porter's handbook says[1] (at greater
lengths that what I'm writing here, but I'm summarizing):

PORTREVISION should be increased each time a change is made to the port.
It is reset each time PORTVERSION increases.  See it as a subversion of a
specific version on the port.

PORTEPOCH is to be used when PORTVERSION goes back.  Say, it goes from
0.19 to 0.2, which, in the upstream developer's mind were really 0.19 and
0.20, but he removed the 0 at the end.  And as 0.19 is greater than 0.2,
which you can check with:
$ pkg version -t 0.19 0.2
>
you have to bump PORTEPOCH:
$ pkg version -t 0.19 0.2,1
<

Because the version of the port *never* decreases.

1:
<http://www.freebsd.org/doc/en/books/porters-handbook/makefile-naming.html#makefile-naming-revepoch>

-- 
Mathieu Arnold