frankie@debian wrote:
Mainly policy compliance and setting up the required framework to manage
smooth plugins updates. I already sent a message about that on the
qgis-dev list. No answers at my knowledge...
Then I would suggest to send .deb version a.b.c-0 to sid/experimental with
plugins (or plugin updates) disabled. This could get the bulk of the non-
plugin packaging issues dealt to and perhaps motivate others to help
with plugin needs.
Do the qgis plugins have a firefox-like addon update structure?? (eek)
If so, can we ship a static snapshot of them? I'd prefer to keep things
in main and just deal with some things being out of date, but perhaps
the volatile repo is another option. Moving targets and external downloads
will not help to get it packaged quickly..