Hi again,
On Tue, Nov 10, 2020 at 10:10:21AM +0100, Alois Schlögl wrote:
>
> Ok, I see. Biosig can be build with any python version (it is just using the
> general API for module extension which is not)
>
> That means, building it for any python version will work like this
>
> (cd biosig4c++/python && python3 setup.py sdist )
>
> (cd biosig4c++/python && python2.7 setup.py install )
This is not needed since python2.7 will be removed.
> (cd biosig4c++/python && python3.8 setup.py install )
> (cd biosig4c++/python && python3.9 setup.py install )
This would be
for py in $(py3versions -s) ; do
(cd biosig4c++/python && $py setup.py install )
> The question is: when packaging this in debian, how to tell which python
> versions are available, and how to trigger the build for that version ?
See above.
> Will there be a python3.8-biosig and python3.9-biosig package, and how does
> this affect debian/control ?
It does not affect debian/control but debian/rules. OK, if you want
the *easy* solutition just use
s/python3-all-dev/python3-dev/
in d/control, which solves the issue since only the default python3
will be used (py3versions -d). This is the *quick* fix for the bug.
It simply depends what you *want* from your users. I hope Michael
or Yaroslav could comment on this. I'm out at this point since I'm
not a user of this package.
> I've reverted the change, and partially fixed the build. Some issues remain
> unsolved - as described before.
Hope this helps. Other hints might be given by [email protected].
Kind regards
Andreas.
--
http://fam-tille.de
