filesystems/py-llfuse 1.5.2

Mk/Uses/python.mk: Remove USE_PYTHON=cython3{,_run,_test}

- Convert all cython3 occurrence to USE_PYTHON=cython*
- Bump PORTREVISION dependent ports of USE_PYTHON=cython_run for dependency change

PR:		291778

filesystems/py-llfuse: devel/py-llfuse: Update to 1.5.2

Changes:	https://github.com/python-llfuse/python-llfuse/releases
		https://github.com/python-llfuse/python-llfuse/blob/master/Changes.rst

filesystems/py-llfuse: use Cython3, add LIB_DEPENDS

Bumping PORTREVISION due to library change.

filesystems: add new category for file systems and related utilities

The filesystems category houses file systems and file system utilities.
It is added mainly to turn the sysutils/fusefs-* pseudo-category into
a proper one, but is also useful for the sundry of other file systems
related ports found in the tree.

Ports that seem like they belong there are moved to the new category.
Two ports, sysutils/fusefs-funionfs and sysutils/fusefs-fusepak are
not moved as they currently don't fetch and don't have TIMESTAMP set
in their distinfo, but that is required to be able to push a rename
of the port by the pre-receive hook.

Approved by:	portmgr (rene)
Reviewed by:	mat
Pull Request:	https://github.com/freebsd/freebsd-ports/pull/302
PR:		281988

devel/py-llfuse: Update to 1.5.1

- Add GitHub to MASTER_SITES

Changes:	https://github.com/python-llfuse/python-llfuse/releases
		https://github.com/python-llfuse/python-llfuse/blob/master/Changes.rst

devel/py-llfuse: Update to 1.5.0

Changes:	https://github.com/python-llfuse/python-llfuse/releases

devel/py-setuptools: convert individual consumers to ${PY_SETUPTOOLS}

Currently a no-op, but in the future outputs the correct setuptools
port depending on whether USES_PYTHON=distutils is specified.

With hat: python
PR: 270510, 270358

devel/py-llfuse: Update to 1.4.4

Changes:	https://github.com/python-llfuse/python-llfuse/releases

devel/py-llfuse: Update to 1.4.3

- Update WWW
- Add LICENSE_FILE
- Convert to USE_PYTHON=pep517
- Convert to USE_PYTHON=pytest
- Take maintainership

Changes:	https://github.com/python-llfuse/python-llfuse/releases

*/*: rename CHEESESHOP to PYPI in MASTER_SITES

PR:			267994
Differential revision:	D37518
Approved by:		bapt

devel/py-llfuse: fix build with clang 15

During an exp-run for llvm 15 (see bug 265425), it turned out that
devel/py-llfuse failed to build with clang 15:

  src/llfuse.c:41839:21: error: incompatible pointer to integer conversion assigning to 'uintptr_t' (aka 'unsigned int') from 'pthread_t' (aka 'struct pthread *') [-Wint-conversion]
          __pyx_v_tid = __pyx_t_7;
                      ^ ~~~~~~~~~
  src/llfuse.c:42467:3: warning: 'PyEval_InitThreads' is deprecated [-Wdeprecated-declarations]
    PyEval_InitThreads();
    ^
  /usr/local/include/python3.9/ceval.h:130:1: note: 'PyEval_InitThreads' has been explicitly marked deprecated here
  Py_DEPRECATED(3.9) PyAPI_FUNC(void) PyEval_InitThreads(void);
  ^
  /usr/local/include/python3.9/pyport.h:508:54: note: expanded from macro 'Py_DEPRECATED'
  #define Py_DEPRECATED(VERSION_UNUSED) __attribute__((__deprecated__))
                                                       ^
  1 warning and 1 error generated.

The conversion from pthread_t to uintptr_t needs an explicit cast.

PR:		268226
Approved by:	maintainer timeout (2 weeks)
MFH:		2022Q4

devel/py-llfuse: update to community 1.4.2, fixing Python 3.11 build

and add a pytest-based test driver (but self-tests appear centered
on Linux's /proc/PID/status interface and fail).

PR:		266201

devel/py-llfuse: reset maintainer, unreachable

This appears, per INDEX-13, to be the only port where
MAINTAINER was set to stdin@niklaas.eu.

PR:		266796

--------------------
Reporting-MTA: dns; mx2.freebsd.org
X-Postfix-Queue-ID: 4MhC8t64n8z3YDm
X-Postfix-Sender: rfc822; mandree@FreeBSD.org
Arrival-Date: Mon,  3 Oct 2022 20:28:46 +0000 (UTC)

Final-Recipient: rfc822; stdin@niklaas.eu
Original-Recipient: rfc822;stdin@niklaas.eu
Action: failed
Status: 5.1.1
Remote-MTA: dns; mx02.mail.icloud.com
Diagnostic-Code: smtp; 550 5.1.1 <stdin@niklaas.eu>: user does not exist
--------------------

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)

devel/py-llfuse: unbreak bulk -a

devel/py-llfuse: limit to Python 3.10; broken on 3.11

since it #include "longintrepr.h" which is disabled in Python 3.11,
see https://docs.python.org/3.11/whatsnew/3.11.html

PR:		266201

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

Remove # $FreeBSD$ from Makefiles.

devel/py-llfuse: Update 1.3.6 -> 1.3.8

PR:		252117
Submitted by:	jcfyecrayz@liamekaens.com
Approved by:	stdin@niklaas.eu (maintainer's timeout 30 days)

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 1.3.6

PR:		242587

Revert r517286, breaking bulk -a is not covered by portmgr blanket

- Limit python version (does not build with 3.7+)

Approved by:	portmgr blanket

devel/py-llfuse: Fix build (warning=error), remove -Werror

-Werror is added to flags by default, breaking build for example with GCC.

Follow upstream and remove it. Also disable DEVELOPER_MODE since it's enabled too widely.

PR:		238887
Approved by:	portmgr (blanket(s): build fix, ports compliance), linimon (mentor)
Differential Revision:	https://reviews.freebsd.org/D21067

Bump PORTREVISION for ports depending on the canonical version of GCC as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3 to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

Bump PORTREVISION for ports depending on the canonical version of GCC defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590

Bump PORTREVISION for ports depending on the canonical version of GCC in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which has now moved from GCC 6 to GCC 7 by default.

This includes ports
 - featuring USE_GCC=yes or USE_GCC=any,
 - featuring USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and those
 - with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
   c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.

PR:		222542

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

Bump PORTREVISION for ports depending on the canonical version of GCC (via Mk/bsd.default-versions.mk and lang/gcc) which has moved from GCC 5.4 to GCC 6.4 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
   c++14-lang, c++0x, c11, or gcc-c++11-lib.

PR:		219275

Provide more descriptive error messages for ports failing on powerpc64.

Approved by:	portmgr (tier-2 blanket)

devel/py3-llfuse: create port

Python 3 version of py-llfuse

devel/py-llfuse: Allow overriding USES

- Update to 1.2 - Update maintainer's email

PR:		218305
Submitted by:	stdin@niklaas.eu(maintainer)

Bump PORTREVISIONs for ports depending on the canonical version of GCC and lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some circumstances such as versions of FreeBSD or platforms).

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using using Mk/bsd.octave.mk which in turn has USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
   c++11-lang, c++0x, c11, or gcc-c++11-lib.

PR:		216707

Do not use post-stage.  Use post-install instead.

The only reason to use post-stage is because the port needs to do
"things" at a later time, like some plist manipulation.
While there, fold post-install in do-install targets when they are
defined.

PR:		214780
Submitted by:	mat
Exp-run by:	antoine
Sponsored by:	Absolight

many ports: mark broken on powerpc64

devel/py-llfuse: Another attempt to fix STRIP

PR:		203759
Submitted by:	jbeich

devel/py-llfuse: fix STRIP_CMD

PR:		203759
Pointy-hat to:	pi

New port: devel/py-llfuse

Python-LLFUSE is a set of Python bindings for the low level FUSE API. It
requires at least FUSE 2.8.0 and supports both Python 2.x and 3.x. It runs
under Linux, OS-X, FreeBSD and NetBSD.

WWW: https://bitbucket.org/nikratio/python-llfuse

PR:		203759
Submitted by:	Niklaas Baudet von Gersdorff <niklaas@kulturflatrate.net>