Drop PORTREVISION, now good to go

Bump PORTREVISIONs, use less problematic patches, bump python to 3.6+

In D23161#507739, @greg_unrelenting.technology wrote:

https://github.com/myfreeweb/freebsd-ports-dank/blob/lite/graphics/mesa-dev/Makefile

Do not bump PORTEPOCH, slightly fix the patch

Remove files that should have been deleted

Keep author (meant to have $FreeBSD$, oops), fix naming and bump ports touched by the patch

Unbreak on i386 by allowing relocations on read-only segments

Rebase diff, while here remove the hardcoded version from other ports

Switch to Java 8, use 2.0.10 and be poudriere-friendly

Switch to fork with dependencies already fetched to avoid poudriere failure

Colorize output and remove --offline as the port has deps

Colorize output and remove --offline as the port has deps

Use correct year (one shall not do PRs at 2AM)

Outdated revision

Shouldn't PORTREVISION be 2 on all of the files?

Committed

https://svnweb.freebsd.org/ports?view=revision&revision=500123

Committed

Add missed i386/conf/MINIMAL, prefer commenting over removing the entire line (to not make people think we removed the feature altogether), add COMPAT_FREEBSD9 as well, correct SVN branch

https://reviews.freebsd.org/rP491270

Remove pkg-plist, extend pkg-descr

Use correct SVN branch

In D18451#396062, @mat wrote:

In D18451#395629, @voidanix_420blaze.it wrote:

@tobik is there any way I can get this port committed? I can't commit this yet :p

This tool, here, Phabricator, is a code review tool, not a patch queue for things to be committed, which is what Bugzilla is for.
If you are not a committer, or do not plan to commit it yourself, it is best to always open a PR on our bugzilla in parallel so that the change actually goes in our pipeline.

@tobik is there any way I can get this port committed? I can't commit this yet :p

Attemp fixes

https://reviews.freebsd.org/D17760

readd bash (why did i remove it in the first place?)

Apply change to i386, PPC/PPC64 and SPARC64 too (@cem 's tip)

In D17375#371509, @debdrup_gmail.com wrote:

I shan't comment on it on the change itself, but have you considered getting some reviewers attached to this?
Changes to FreeBSD typically don't land automatically, and there usually has to be at least some sort of review process.

how do i svn dud