py-pyqrcode 1.2.1: unmaintained software

[harens (Haren S)]

​pyqrcode has not been updated since early 2016.

A fork of this, ​pyqrcodeNG, has been updated as recently as April 2020. This is what is currently being packaged by openSUSE in both ​Tumbleweed and ​Leap 15.2 in preference to the standard pyqrcode.

However, even this is now unmaintained, and the ​README instead suggests ​segno as an alternative. I personally think that the current pyqrcode port should be made obsolete and that one of the two substitutes should be added instead (I'd be happy to write a portfile for it), although I'm interested to hear what anyone else thinks.

[herbygillot (Herby Gillot)]

Hey harens, thanks for the heads-up.

I think that we can certainly have a separate port for pyqrcodeNG, but it won't be a drop-in replacement for packages depending on pyqrcode as it doesn't export the same package name. Software would have to be patched or updated upstream. If we have a separate port for pyqrcodeNG, I don't think that's good enough, and we don't have to mark the original pyqrcode port as obolete, but just leave it as is. We could mark it obsolete if and only if the port replacing it exports the same package name, making it a completely transparent switch for dependent ports.

[harens (Haren S)]

Thanks for your reply herbygillot. You make a very good point regarding dependant ports, which I completely agree with.

I don't think it should be that hard to write portfiles for both alternatives. The portfile for pyqrcodeNG should be nearly identical to pyqrcode, and segno has no dependencies which should make things very straightforward. As I said before, I'd be more than happy to write both of them and I will start doing that now, although I don't know whether you would like to be a maintainer/co-maintainer for pyqrcodeNG?

[herbygillot (Herby Gillot)]

Feel free, harens. No need to add me as co-maintainer. As a matter of fact, I am actually considering transitioning all Python ports currently under my maintainership to nomaintainer, which should make it easier for folks to make updates directly to them as needed, and not require a PR or maintainer approval.

Thanks for looking into this.

[herbygillot (Herby Gillot)]

Clarifying the previous, I meant nomaintainer for Python library ports. For actual Python CLI tools or utilities, they would stay as-is.

[harens (Haren S)]

In 1a235702aacfc180852245a814264caf8e208be6/macports-ports (master):

py-pypng: add python 3.9

See: #61342

[harens (Haren S)]

In 047358ba3c3d272387393ff1caa7f1330120c1d9/macports-ports (master):

py-segno: new port

See: #61342

Co-Authored-By: herbygillot <herby.gillot@…>

[harens (Haren S)]

In f8138a16953ba2697c76e43e17f90a296621ce30/macports-ports (master):

py-pyqrcodeng: new port

Closes: #61342

[harens (Haren S)]

Thanks herbygillot for your help.