Forking a couple of python ports to tauthon versions

Hey there all, I’m looking at *attempting* to get Mailman to play nice with tauthon, but the dependency chain is kind of fierce: dnspython, cython, setuptools. I’d like to do this in a ports-compatible way if at all possible. /usr/ports/Mk/uses/Python.mk will never include tauthon as a version

Re: How does the pkg version syntax work?

Hi Eugene, That one does not actually really explain how the syntax works. It gives a bunch of examples but does not systematically explains how it works. Additionally, the explanation is incomplete (e.g. it's completely silent about how + works and the special cases for letters in version number

Re: How does the pkg version syntax work?

15.07.2022 1:42, Robert Clausecker wrote: > The ports collection generates a PKGVERSION from the DISTVERSION or > PORTVERSION provided by the port. This PKGVERSION is then used to > decide whether one package is newer or older than the other. > > However, it seems to be poorly documented. https

Unmaintained FreeBSD ports which are out of date

Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. Please consider also adopting this po

How does the pkg version syntax work?

The ports collection generates a PKGVERSION from the DISTVERSION or PORTVERSION provided by the port. This PKGVERSION is then used to decide whether one package is newer or older than the other. However, it seems to be poorly documented. There does not seem to be any documentation in the man pag