--
Greg Freemyer
Advances are made by answering questions. Discoveries are made by
questioning answers.
— Bernard Haisch
On Thu, Jun 29, 2017 at 8:39 AM, jan matejek
Hello,
Note none of the modules are exclusively available as python3. What happens when the first of those dependencies goes python 3 only?
there is no reason to think any of them would go python3-only, unless upstream drops support. If/when the packages are singlespecced, python2 versions will still be available.
If this does happen, then your package would break, and you would need to separately maintain an old version of that package which is still compatible with python 2.
does this answer your question?
I fear so. My question related to your earlier statement:
So "python2-foo" is fine, "python3-foo" is fine, "python-foo" which is not singlespec is rejected.
On its face I could address that requirement in python-liblnk by modifying the specfile to appropriately produce python3-liblnk instead. Unfortunately I take your answer to say that will break python-plaso currently. Thus I now know the only viable solution is to do what I've done in libsmdev as an example and ensure both python2-smdev and python3-smdev are available, the create a version free tag (pysmdev) that both of them provide and have python-plaso require: pysmdev. There's about 20 c library packages with python bindings I maintain outside of d:l:p. None have been adjusted for singlespec. They all have similar spec file structures. Perhaps I can ask you to adjust libsmraw in security:forensics to use singlespec, then I can replicate it to the others. Alternatively, libsmdev was my pre-singlespec effort to add dual python2/python3 support. Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org