net/py-miniupnpc 2.3.1_1

python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal

Any missed ports, feel free to bump.

Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.

all: remove explicit versions in USES=python for "3.x+"

The logic in USES=python will automatically convert this to 3.8+ by
itself.

Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.

finance/quickfix: mark BROKEN with PYTHON

libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++ -DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable -Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong -fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi -Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings -Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x -MT _quickfix_la-QuickfixPython.lo -MD -MP -MF .deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp  -fPIC -DPIC -o .libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
          ^~~~~~~~~~
1 warning and 1 error generated.

Reviewed by:	portmgr, vishwin, yuri
Differential Revision:	<https://reviews.freebsd.org/D40568>

net/py-miniupnpc: Add CPE information

Approved by:	portmgr (blanket)

One more small cleanup, forgotten yesterday. Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

Drop python 2.7 support from a few ports

With hat:	portmgr

Relax hardcoded paths to fix build with Python 3.8.7

Since r558913 Python 3.8 incorporates BPO-42604 [1] which changed the
shared libs naming scheme.  This means "EXT_SUFFIX" is now derived from
SOABI and yields with Python 3.8 to ".cpython-38.so" instead of ".so".

The affected ports strip the libaries in the "post-install" target via
hardcoded path(s) and the build fails at the end because the new extension
is not expected at this place.

Remedy the issue by adding wildcards to these paths.  This should also
prepare the ports for future Python releases, which will use the new shared
libs naming scheme.

[1] https://bugs.python.org/issue42604

PR:		252057
Reported by:	John Kennedy
Reviewed by:	fluffy, koobs
Approved by:	koobs (python)

- update to miniupnpc 2.1 PR:		228050 Submitted by:	Hung-Yi Chen

- fix python build
- add LICENSE for slave port
- make portlint happier

- bump PORTREVISION on ports using the shared lib

Remove the use of submake, and use the parent's port shared library instead.

While there, remove an obsolete sed line that does not match anything.

Sponsored by:	Absolight

Fix after empty FLAVOR as make argument was forbidden

Convert Python ports to FLAVORS.

Ports using USE_PYTHON=distutils are now flavored.  They will
  automatically get flavors (py27, py34, py35, py36) depending on what
  versions they support.

  There is also a USE_PYTHON=flavors for ports that do not use distutils
  but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
  using distutils but flavors are not wanted.

  A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
  added to cope with Python ports that did not have the Python
  PKGNAMEPREFIX but are flavored.

  USES=python now also exports a PY_FLAVOR variable that contains the
  current python flavor.  It can be used in dependency lines when the
  port itself is not python flavored.  For example, deskutils/calibre.

  By default, all the flavors are generated.  To only generate flavors
  for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
  BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.

  In all the ports with Python dependencies, the *_DEPENDS entries MUST
  end with the flavor so that the framework knows which to build/use.
  This is done by appending '@${PY_FLAVOR}' after the origin (or
  @${FLAVOR} if in a Python module with Python flavors, as the content
  will be the same).  For example:

    RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}

PR:		223071
Reviewed by:	portmgr, python
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D12464

Fix ports setting WRKDIR themselves to use the new _WRKDIR instead of the litteral "work".

I think it should be really safe to remove both instances because they
they point to directories that are empty anyway.

With hat:	portmgr
Sponsored by:	Absolight

Remove ${PORTSDIR}/ from dependencies, categories m, n, o, and p.

With hat:	portmgr
Sponsored by:	Absolight

- Makefile.local for slave ports is included by bsd.port.mk r397519

- Switch to USE_PYTHON=autoplist to fix stage-qa problem with .egg-info files handling

Approved by:	portmgr blanket

- update miniupnpc to 1.9 - bump users of shared lib version PR:		194031

- fix misplaced NO_STAGE in slaveports and ifdefs

Add NO_STAGE all over the place in preparation for the staging support (cat: net)

- cleanup header

- fix package after update PR:		162368 Submitted by:	Jan Beich Feature safe:	yes

- Mark BROKEN: does not package   Writing /usr/local/lib/python2.7/site-packages/miniupnpc-1.5-py2.7.egg-info   [..]   tar: lib/python2.7/site-packages/miniupnpc-1.6-py2.7.egg-info: Cannot stat: No such file or directory

Reported by:	pointyhat

- add py-miniupnpc to python category. PR:		137756 Submitted by:	Anonymous

Python module for miniupnpc

The usage of the miniUPnP client library is useful whenever an application
needs to listen for incoming connections.
Examples : P2P applications, FTP clients for active mode, IRC (for DCC)
or IM applications, network games, any server.

WWW: http://miniupnp.free.fr/
PR:		137612
Submitted by:	Anonymous