Comment 5 for bug 1636945

It will also be interesting to see whether there are remaining bugs in aptcc that should be fixed.
In general, aptcc is much slower than it needs to be, mainly due to its really ineffective cache handling (reopening it again and again for most transactions) and old code that was copied from various places (apt-get, Synaptic, even aptitude).

I wanted to fix the caching issue at some point, but that would as of now amount to massive refactoring - we even discussed briefly with KDE Neon people the possibility to do a clean rewrite of PKs APT backend (quite some effort), which might be a possibility in the future.

In any case, there are currently no known major bugs in aptcc, except for its slowness and inability to parallelize read transactions (the latter was due to APTs limitations in the past, and the APT guys say it might be possible now - unfortunately, aptcc itself isn't ready for that, due to having been developed non-threadsafe for a long time :P)

In any case, on topic: Thanks Robert for working on updating GS!