notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
This referral link gives you 10% off a Fastmail.com account and gives me a discount on my Fastmail account.

Get notified when packages are built

A new feature has been added. FreshPorts already tracks package built by the FreeBSD project. This information is displayed on each port page. You can now get an email when FreshPorts notices a new package is available for something on one of your watch lists. However, you must opt into that. Click on Report Subscriptions on the right, and New Package Notification box, and click on Update.

Finally, under Watch Lists, click on ABI Package Subscriptions to select your ABI (e.g. FreeBSD:14:amd64) & package set (latest/quarterly) combination for a given watch list. This is what FreshPorts will look for.

non port: devel/py-interface-meta/Makefile

Number of commits found: 4

Tuesday, 4 Apr 2023
18:29 Antoine Brodin (antoine) search for other commits by this committer
USE_PYTHON=pep517: bump PORTREVISION
commit hash: 1730e97e049085a8fe5536788d214cbfc4eb3123 commit hash: 1730e97e049085a8fe5536788d214cbfc4eb3123 commit hash: 1730e97e049085a8fe5536788d214cbfc4eb3123 commit hash: 1730e97e049085a8fe5536788d214cbfc4eb3123 1730e97
Sunday, 5 Feb 2023
19:05 Charlie Li (vishwin) search for other commits by this committer
Revert "Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install
bytecode"

Despite installer's default behaviour to compile and install bytecode,
we are not doing so going forward at stage/package time. [0] During
initial development and qualification of PEP-517 framework support,
compiling and installing bytecode at stage/package time was considered,
but was found problematic, fragile and ultimately unreliable, both
currently and historically (with USE_PYTHON=distutils), due to our
fixed plist requirement. While the living binary distribution format
(wheel) specification [1] says to compile bytecode, that is in the
pure Python package management context (pip, etc); nuance always
exists when interacting with "system" package management.

Additionally, "bytecode is an implementation detail of the CPython
interpreter. No guarantees are made that bytecode will not be added,
removed, or changed between versions of Python," thus "should not
be considered to work across Python VMs or Python releases." [2]
This is important to ensuring correctness for those ports specifying
NO_ARCH.

Instead of compiling and installing bytecode at stage/package time,
there is a WIP, review D34739, that compiles and installs bytecode
at install time instead, using triggers.

The aforementioned build_fs_violations will be investigated.

This reverts commit de6965254c3a007efcf697c3d455b54d2aeb2383.

With hat:	python
Approved by:	tcberner (mentor, portmgr)
Reference:	https://wiki.freebsd.org/Python/PEP-517 [0]
		https://packaging.python.org/en/latest/specifications/binary-distribution-format/
[1]
		https://docs.python.org/3/library/dis.html [2]
commit hash: f5890bd3cbc66a805bfc04a1a45688b5a3e68c50 commit hash: f5890bd3cbc66a805bfc04a1a45688b5a3e68c50 commit hash: f5890bd3cbc66a805bfc04a1a45688b5a3e68c50 commit hash: f5890bd3cbc66a805bfc04a1a45688b5a3e68c50 f5890bd
18:16 Po-Chuan Hsieh (sunpoet) search for other commits by this committer
Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install bytecode

- While I'm here, use long options for easier reading [1][2]
- Bump PORTREVISION of dependent ports (USE_PYTHON=pep517) for package change

It fixes build_fs_violation of dependent ports in poudriere (with -t flag).
It is also the default behavior of installer [2].

from py-sphinx log:
=>> Checking for staging violations... done
=>> Error: Filesystem touched during stage (files must install to ${STAGEDIR}):
extra: usr/local/lib/python3.9/site-packages/importlib_metadata/__pycache__
=>> Cleaning up wrkdir

from installer documentation:
--compile-bytecode
    Possible choices: 0, 1, 2
    generate bytecode for the specified optimization level(s) (default=0, 1)
--no-compile-bytecode
    don’t generate bytecode for installed modules
    Default: False

With hat:	python
Reference:	https://pypa-build.readthedocs.io/en/stable/ [1]
		https://installer.pypa.io/en/stable/cli/installer/ [2]
commit hash: de6965254c3a007efcf697c3d455b54d2aeb2383 commit hash: de6965254c3a007efcf697c3d455b54d2aeb2383 commit hash: de6965254c3a007efcf697c3d455b54d2aeb2383 commit hash: de6965254c3a007efcf697c3d455b54d2aeb2383 de69652
Saturday, 4 Feb 2023
06:58 Yuri Victorovich (yuri) search for other commits by this committer
devel/py-interface-meta: New port: Expose an extensible API with enforced method
signatures
commit hash: 4a39c486b8338ecbfd0de60109cc27a9206c9ca2 commit hash: 4a39c486b8338ecbfd0de60109cc27a9206c9ca2 commit hash: 4a39c486b8338ecbfd0de60109cc27a9206c9ca2 commit hash: 4a39c486b8338ecbfd0de60109cc27a9206c9ca2 4a39c48

Number of commits found: 4