Created attachment 219669 [details]
Resurrect py-rrdtool_lgpl based on https://github.com/commx/python-rrdtool and take maintainership.
The reason this port was removed was, that it uses EOLed python27.
Did you try if it works with Python >= 3.6?
Yes, I tested this with Python 3.7 and it work for my use case (a Python script to log stats from my VDSL modem)
Please rework the Makefile, use portlint and see below.
As far as I can tell this falls under https://wiki.freebsd.org/Python/PortsPolicy and all of its recommendations.
Please submit patches as .patch of .diff files, not compressed.
After looking at it a bit longer, I'm not sure if it's right to revive a port in this case. The new port comes from completely different sources, but has the same function.
Also, I think that in case of a new port a naming scheme like py-python-rrdtool or maybe py-rrdtool would be more appropriate.
Is it possible to create some kind of 'sub port' to rrdtool that just compiles the Python extensions?
That way non-Python users are not lumbered with them but they are available via pkg.
I can do the work but if you are aware of a port I can crib the idea from that would be very helpful.
(In reply to darius from comment #5)
> Is it possible to create some kind of 'sub port' to rrdtool that just compiles the Python extensions?
I don't see anything else besides the python extension, actually.
Anyways, the port should leverage usual USES=python infrastructure and get distribution files from PyPI (CHEESESHOP).
The port would look much like devel/py-hg-evolve that rhurlin@ ported recently.