Hi Santiago, Am Thu, Nov 28, 2024 at 09:30:15AM -0300 schrieb Santiago Ruano Rincón: > > Many GNU packages have built-in tests that test the just-built programs.
This reminds me to my attempt to write some autopkgtest for tar. I've created an according bug report[1] (in CC) but I did not went really far to run the upstream test suite in an autopkgtest. I needed some local header files from the build which is definitely not a good idea and the final autopkgtest failed even then[2]. Currently I have no time to continue with this. However, if someone wants to add an autopkgtest to one of our most used packages this would be great. Kind regards Andreas. > > Is there a general procedure/trick/idiom to modify them so that they test > > the installed version instead? (so that they can be reused with minimal > > changes). > > > > (I'd like to do this for several packages without reinventing the wheel). > > This is what grep does [0]: > > #!/bin/sh > set -e > > export DEB_BUILD_PROFILES="nocheck nodoc" DEB_BUILD_OPTIONS="nocheck > nodoc" > > dpkg-source --before-build `pwd` > dpkg-buildpackage -rfakeroot --target=clean > dpkg-buildpackage -rfakeroot --target=build > > make -C tests check-am > > [0] > https://salsa.debian.org/debian/grep/-/blob/9f6e70143249f6c92fb7158a74d288332e132df4/debian/tests/upstream-test-suite [1] https://bugs.debian.org/1068576 [2] https://salsa.debian.org/debian/tar/-/jobs/5494107 -- https://fam-tille.de
