[Bug 251126] Resurrect databases/py-rrdtool_lgpl

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Dec 6 14:05:37 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251126

--- Comment #7 from Rainer Hurling <rhurlin at FreeBSD.org> ---
Created attachment 220310
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=220310&action=edit
patch with new, not resurrected port

Hi Daniel,

Inspired by comment #6 I created a port that should work as expected.

Some decisions had to be made:

- The port should not be a further development of the former port
databases/py-rrdtool-lgpl, because the naming does not fit well and the former
port was based on other sources

- Um zukünftige Updates zu erleichtern, soll der Sourcecode von Pypi bezogen
werden

- While the original source on Github is called python-rrdtool [1], the project
page on Pypi [2] and the tarball there are only named rrdtool. The port should
be fully named as on Github, plus the prefix depending on the Python version.
So that CHEESESHOP can find the source, a part of PORTNAME had to be moved to
PKGNAMEPREFIX

- I have extended the text in pkg-descr with information from the github page.
Also the URL now points to the original source


[1] https://github.com/commx/python-rrdtool
[2] https://pypi.org/project/rrdtool/


IMPORTANT: 
I think it would be useful if the port would additionally inform that the
Python bindings can also be installed by enabling the OpTION PYTHON in the main
port databases/rrdtool. But this should not be done if the Python bindings are
to be installed via databases/py-python-rrdtools.


What do you think about all this? If you agree in principle, it would be nice
to test this proposal for the port. If the port builds, installs, and if it
works as expected with rrdtool ...

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list