Hi Jonas,
How are you doing with the packaging?
What steps have been done? What's left on your list?
I released a v0.58.0 which would be the last one with Python 3.5
support.
I am planning a v0.60.0 which drops Python 3.5 and uses Scrypt from
v3.6 standard library.
Silkaj v0.8.0 distribution to PyPI will stay on DuniterPy v0.58.x to
keep Python 3.5 support.
Silkaj v0.8.0 package on Debian Bullseye will use DuniterPy v0.60.0
since Python 3.8 is used from Debian.
Regarding DuniterPy v0.60.0, is there any requirement or wish from your
side for the packaging, for
us to include it into this release?
One thing that we need to clarify on our side is about the copyright
and license
statements usage in the headers of every files.
In our discussion for Silkaj packaging for Debian Buster, you told me
that this how the GPL licensing
should be used.
For our understanding, is it a requirement from Debian packaging or
from the GPL licensing
guidelines? One answer can be that Debian packaging requires to follow
the licenses guidelines.
Can you confirm that these statements have to be prepend to every file?
The runtime source code should have them of course. Does the tests and
the examples should also have those
statements?
Does the tests and the examples will be distributed in the package?
The related ticket:
<https://git.duniter.org/clients/python/duniterpy/-/issues/111>
DuniterPy v0.60.0 is the release which should be packaged in Debian
Bullseye. Of course, we can make
v0.60.x releases if necessary.
Best regards,
Maël
