Hi all.  I'm sorry to have been unresponsive to this bug.  I agree it is
a problem, and I'd like to help fix it.

I propose unifying the desktopcouch, python-desktopcouch, and
python-desktopcouch-records packages, into one desktopcouch package and
two empty transitional* packages.  There's too much interdependency for
them to be separate, so discrete packages doesn't make much sense.

So, the present

desktopcouch-tools
desktopcouch
python-desktopcouch
python-desktopcouch-records

will become

desktopcouch-tools
        (no change)
desktopcouch
        (+ contains all library files also)
        (- Depends on python-desktopcouch, python-desktopcouch-records)
        (+ Provides python-desktopcouch, python-desktopcouch-records)
python-desktopcouch
        (- all files)
        (+ Depends on desktopcouch)
python-desktopcouch-records (+depends on desktopcouch
        (- all files)
        (+ Depends on desktopcouch)


Does this sound acceptable?

Speaking as Upstream, I will have these code dependencies severed before
long.  I wasn't thinking as a packager when I approved or wrote the
current code.

- Chad Miller


* Empty packages with new Depends?  I know of "Provides" in Policy, but
I don't know enough about its sufficiency for real, non-"Virtual" packages.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to