
On samedi, 13 août 2016 10.33:00 h CEST Michael Ströder wrote:
HI!
Any reason why so many Python module packages have the misnomer python-python-* as package names? And the set of this misnomers even grow.
Since ages the convention is that a distribution package name of a Python module should be "python-<import-name>". This convention is wildly violated. And it makes authors of cross-platform ansible plays, puppet modules, chef receipts, etc. even more miserable.
Ciao, Michael.
After reading the whole thread, I would like to try to summarize it a bit so we can decide as a community how we can move forward. 1) We have a tool python-py2pac and almost python3-py2pac https://github.com/saschpe/py2pack https://github.com/saschpe/py2pack/issues/59 As Sacha is not that more active in our packaging community, I would tend to believe it would be cool to have 1.a : A brave maintainer of d:l:p / d:l:p3 fork it, see how it can be improved and propose it as a tool inside https://github.com/openSUSE So it become a tool for everybody 1.b : Point to that tool location inside our Python(3) wiki page 2) Michael remark about python-python-* I remember myself being refused on sr with python3-dateutils :-) I'm using a lot of system require for any python's stuff deployed here. I didn't see a python module not being able to use those system deployed. But I've not a overlong list of requires, and moreover all of are python3. 2.a Michael if you have a list of precise packages that failed to fullfill those provides/requires could you create a list ? Would be really useful to get it writen down in bugzilla and bring back the number here, or in worse case, bring the list here. I will try to then create that bug. 3) Python / Python3 : How to fix our mess, and create a bright future. If packaging can be fun, the inverse can be true. I believe we are the last community that package python 2 et python 3 version in a separate way. This has already cause some grief, and we really need to fix it, no? I've already heard that there's reasons behind the choice made. But we lack the fundamentals, as they are not clearly explained on obs project's page, nor in the wiki. So if new comer, like me arrived and try to understand how it works, you spend too much time on guessing and SR try and errors. With the py2/py3 split, we also tend to forget to update one or the other repository (py2pack need to be fixed and improved to handle that), and we also have constants divergences between the 2 specs, which will increase errors, lost tracking bugs, or have version specific bugs. This will (or did it already) kill any efforts to bring new hands to help. Ease our live (packager, users, bugfix & so on), and also get a coherent eco- system around python technology. 3.a What about opening a real discussion about our Python situation - Be it here on packaging list with a simple [python] prefix in the subject - Be it on a discussion page in the wiki (if editing is now fixed) - Be it (creative minds your input here) * I'm really interested by feedback or thoughput of SUSE's employee in charge of LTS support. More we will work together, better the solution will be. 3.b Prepare a kind of RFC for Python at openSUSE - Publish (even on news) and explain where comments should goes, so we can track and pick the good ideas - Organize obs structure to handle the changes (hello obs guru) - Put the changes in action (Hey why not then a pyckaton for that stuff?) We don't need a super-heros here, I'm more confident in the fact that a team that want to achieve a collective forward can make it better than any individual effort. 4) Any stuff I've forget Because I'm too new in python world, I've certainly forget things. Be this paragraph yours. Hope this message, can help our collective effort to make openSUSE the greatest choice OS. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org