Hi,
On Tue, Aug 27, 2019 at 8:09 AM Xavier wrote:
>
> This can be workaround using a "manifest"
Starting with commit 64a7ccd2, t/bin/build-test-packages builds test
packages only when their sources have changed. The sources are
generated from templates and the test specifications. For each test,
Hi,
On Tue, Aug 27, 2019 at 8:09 AM Xavier wrote:
>
> This can be workaround using a "manifest"
That's exactly what is coming.
Le 27/08/2019 à 16:54, Chris Lamb a écrit :
> Hi Xavier,
>
>> an idea to build only needed test packages (and rebuild only needed
>> ones): use a Makefile to detect changes in t/tags/checks.
>
> I suspect this isn't enough given for production caching in that these
> packages are built using the
Hi,
On Tue, Aug 27, 2019 at 7:57 AM Chris Lamb wrote:
>
> it might be fine locally when you know it hasn't changed.
I have something in the works that will use per-test checksums to
restore behavior that was lost when building was split from testing. I
assure you the current situation is a probl
Hi Xavier,
> an idea to build only needed test packages (and rebuild only needed
> ones): use a Makefile to detect changes in t/tags/checks.
I suspect this isn't enough given for production caching in that these
packages are built using the installed toolchain (see t/bin/build-
test-packages-if-n
Package: lintian
Version: 2.19.0
Severity: wishlist
Hi all,
an idea to build only needed test packages (and rebuild only needed
ones): use a Makefile to detect changes in t/tags/checks. Here is a
template that seems to work:
#!/usr/bin/make -f
TAGS:=$(shell find t/tags/checks/ -name desc
6 matches
Mail list logo
