Problem 1: building dependencies
dependencies are our most Debian-style Debian packages: we have one folder per package, that essentially contains all of the
debian/ part of the packaging and we merge that with the unpacked gem as part of our Jenkins build jobs (this is the non-standard part, Debian by default stores the tarballs next to the packaging recipe).
Nevertheless the addition of new packages is a multi-step process that should be automated away, as the current process is prone to subtle errors, especially around folder naming and dependency handling.
Problem 2: building plugins
plugins is what the average developer touches most, when they release new versions and thus bump packaging. Pure bumping is scripted and thus easy. However, every now and then a plugin adds webpack/nodejs/api/you name it and package builds need adjustment as we don’t use tempaltes/macros as heavily as in RPM.
See https://github.com/theforeman/foreman-packaging/commit/f759b4a07302c45787cbad05680b7cb46a057c22 for an example of changes that were needed “just because discovery now uses nodejs”
I’ve deliberately left out Foreman core here, as I think while it could use some improvement, this is something that not everyone needs to touch (today) and thus the benefit of investing time here is smaller.
Please, everyone, speak up where you did spend most time/frustration on in Debian land, so we can tackle those portions.