---------------------------
This is a snapshot in the middle of a big refactoring...
I'd love to use py2deb in a dozen places but was blocked from doing so because
of a handful of unrelated issues that remained to be solved. After lots of
testing, failed attempts and frustration I now have something that seems to
work (although I have to clean it up and there are still some minor issues that
I'm aware of):
- My original goal with py2deb was to use two name spaces for the names of
generated packages: The real name space ``pl-python-...`` would be very
explicit but dependencies would refer to virtual packages named
``python-...``. Then the ``pl-python-...`` packages could have ``Provides:``
fields giving the ``python-...`` names.
It turns out this cannot work the way I want it to; virtual packages are
second class citizens in Debian :-(. AFAICT the only way to get everything
working properly is to just use the ``python-...`` name space directly, so
that's what the new code is slowly working towards.
- Merging of control files was not working properly, however some months ago (I
think before py2deb was born) I wrote my own control file merger. I've now
extracted that from the project where it originated and moved it to a package
called deb-pkg-tools_, which hasn't been released yet but will be soon. py2deb
now uses deb-pkg-tools to patch/merge control files.
- The Python ``==`` version matching operator was copied verbatim to the
Debian control files which is invalid. This is now fixed.
- stdeb_ 0.6.0 is required on Ubuntu 10.04, stdeb 0.6.0+git is required on
Ubuntu 12.04, however stdeb 0.6.0+git hasn't been released yet. Also Python
nor Debian can simply/elegantly express this *very explicit* distinction
between stdeb versions and Ubuntu distributions. The only remaining way to
keep my sanity was to bundle both versions of stdeb inside py2deb.
TODO: Add READMEs, LICENSEs.
- Lots of changes to logging including the version of coloredlogs and the
introduction of separate loggers for separate modules.
- Lots of moving around with code and responsibilities while I tried to make
sense of the way py2deb should and could work.
.. _Release 0.7: https://github.com/paylogic/py2deb/compare/0.6.10...0.7
.. _deb-pkg-tools: https://pypi.org/project/deb-pkg-tools/