On Thu, Jun 13, 2019 at 8:51 AM Dmitry Bogatov <[email protected]> wrote: > > It would be great to ... avoid rebuiling package at every job run.
I would be nice to see how other projects deal with this issue. There is some support for uploading the test packages separately. [1] For Lintian, however, I would prefer to upload the test packages separately to Debian's regular build infrastructure. The test packages can and do have conflicting build dependencies and architectures. These conflicts are not addressed currently, and may require separate chroot build environments. It would be difficult to implement even in a single bulk package. Debian's infrastructure, on the other hand, is designed to build the packages. At the same time, separate uploads would place an undue burden on the archive's namespace and on the NEW queue. There would also be delays for new tags, as Lintian may at some point require that tags are tested. All test packages would have to be in the archive before the lintian source is uploaded. Right now, my favorite solution would be for the archive to offer dependent namespaces for source packages (such as lintian/...). Such internal packages could be uploaded separately and would not have to go through the NEW queue. Outside packages could not depend on them, but they would be installed if their source package requires them. This idea will likely generate much opposition. Let me just say that I am not sure my suggestion is worth the effort, or useful for anyone else. Kind regards, Felix [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926409#42
