LGTM

Bumped .Dd at the beginning of the man page

Update man page

Tested and can confirm this resolves the issue of endless loop with PF_POOL_STICKYADDR when all available ephemeral ports are exhausted.

Bump PORTREVISION

In D16605#353032, @koobs wrote:

Except for this probably requiring a PORTREVISION bump since the package contents are changed, it appears fine, assuming *all* the lines being removed are relevant to that GCC_RUNTIME.

Though I can make a few assumptions (guesses), I'm not familiar enough with the port or that ex.script mechanism to know

Updated patch for devel/ipython

In D16508#351167, @rm wrote:

There are some ports except the jupyter that depend upon ipython and some of them may be python 2.x only, so need to check that too

In D16508#351170, @koobs wrote:

@farrokhi Can you rebase your changes after @rm's commit and update the diff here

Thanks @rm. Could you please then repocopy ipython to ipython5 so that we can apply this patch to ipython?
I am currently testing to make sure these two ports are not installing conflicting files and if they can be installed concurrently.

While we were working on this, @rm committed an update to devel/ipython. It seems he is maintaining 5.x series [2] (which still supports python 2.7) , while the new 6.x series [3] are not still in ports tree.
Now should we repocopy the devel/ipython to devel/ipython6 and turn this patch into a new port?

In D16508#350796, @mat wrote:

The only time you can remove concurrent is when a port supports only one version of Python, say, USES=python:2.7. In any other combination, here, for examples, packages for 3.4, 3.5, 3.6 and 3.7 can be built at the same time.

Restore concurrent flag

In D16378#349810, @dbn wrote:

FYI, commit messages require the full path to this review (your draft message [I assume] only includes the review number)

Remove unnecessary version check for FreeBSD < 10

Remove another unrelated patch that was accidentally slipped in