Digikam git builds use `kde:digikam` however the tarball is actually based on `kde:digikam-software-collection`. To mitgate this we have debian/rules mangle everything so it is like we started with d-s-c. This is not only very unreliable it also bypasses the actual source building code of the tooling.
- digikam git builds should watch and generate off of the d-s-c repo
- the builds will need to run a script in that repo to pull the sources for the collection. tooling currently has no tech for this, but a if-branch in the source could do for now (in the future a simple system should be devised)
- the jenkins jobs somehow also need to have `kde:digikam` as a git repo so it can detect actual source changes to integrate! It doesn't have to clone or use the source, but it absolutely needs to somehow be aware of it so it can perform polling on the repo and get notified of changes.