Status Quo

• source repo of job is digikam.git
• debian/rules upon clean gets digikam-software-compilation, runs its get-repo thing, copies code in place
• push complete content into existing orig tarball

Problems

• only watching digikam.git means kipi changes can't cause rebuilds, which is slightly unfortunate but not too big a problem
• debian/rules' clean target manually lists what should be copied into place
• debian/rules' clean does not strip .git blowing up the tarball substantially
• debian/rules' clean also pushes debian/ itself into the orig.tar, which is somewhat naughty but otherwise not too problematic

Improvements

• the job should use digikam-software-collection.git as source, so we can stop copying things about
  • to monitor for changes either the tooling's Project class needs an extension to support multiple sources? we'd then have source/ source1/ source2/ etc. in the job, but continue to only use source/, source<1-N> only are used for polling purposes
• debian/rules should make sure to remove all .git and not tar debian/

Task can be split into subtasks for the polling bit and the debian/rules bits