Hi, I had a look at the current state of the buildbot and buildbot-slave source packages. It looks like the choice was made to have one source package per binary package.
https://tracker.debian.org/pkg/buildbot https://tracker.debian.org/pkg/buildbot-slave All buildbot related code is under source control in a single git repository. If I understand correctly the way Debian packaging works, there can be multiple bin packages produced from a single source package. This would make sense for buildbot. Even more now that there are multiple web ui plugins that can be installed separately. No need to maintain multiple packages would be simpler. There is one major problem: all www plugins require building coffeescript and jade templates into pure javascript. This requires nodejs and a ton of dependencies (managed by gulp). Simevo created a page on debian wiki to track these: https://wiki.debian.org/Javascript/Nodejs/Tasks/guanlecoja Also, there is an on-going discussion to replace coffeescript by native ECMA6 javascript and switching from gulp to webpack which would remove a lot of these dependencies. Unfortunately, this will take some time to land as this almost means rewriting the whole frontend plugins. In the meantime, I feel that we should drop the buildbot-slave source package and build both buildbot and buildbot-worker binary packages from the buildbot source package. The www plugins can be added later when building them is actually feasible with debian dependencies. Martin, Matthias, what do you think? I'd like your opinion before proceeding in any direction. -- Robin
