Code review comment for lp:~barry/oneconf/lp1088536
Revision history for this message
| Barry Warsaw (barry) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I'm turning this back to a Work In Progress. The issue is that Software Center imports oneconf modules directly, and because it's port to Python 3 is blocked on Xapian (sigh), SC for now still needs Python 2 versions of the modules.
What I propose is to split oneconf into three binary packages:
python-oneconf - the Python 2 version of the core library, usable by SC until its port is complete
python3-oneconf - the Python 3 version of the core library
oneconf - the bin scripts and other stuff