Re: autopkgtest with additional data files?
"Maarten L. Hekkelman" <[email protected]>
| Newsgroups | gmane.linux.debian.devel.medical |
|---|---|
| Message-ID | <[email protected]> |
Op 26-10-2024 om 21:15 schreef Nilesh Patra: >> For one of my projects (density-fitness) I'd like to have a better >> autopkgtest that does not require a full installation of libcifpp along >> with the 750MB of data in components.cif (CCD). So I rewrote the script >> to run the executable in order to use a small subset of that CCD file. >> But the autopkgtest cannot find the file which means the script is not >> run from within the directory where the test files are located. >> >> What is the best approach to fix this? Use the path of the script >> querying $0? Use some undocumented variable to find the location of the >> scripts? Include the data into the script and write that out first >> before running the actual test? > You would need to copy the files to AUTOPKGTEST_TMP dir for them to be > found. The idea is to do the tests in a tmpdir. > I have fixed a patch to salsa, LMK if that makes sense. Thanks, so the script starts in the extracted debian source directory. Should have thought of that. > BTW the cross-builds are failing due to running mrc from build > architecure. Is this really needed/good to have? > (adding -DUSE_RSRC=OFF makes cross builds pass) > > If it does add value, it is fine to have it as is and let cross-builds Well, I think using mrc adds value. It makes executables more portable since some of the most often needed resource files are then included in the binary. But maybe I should drop this feature for packaging in Debian. No one is going to copy a binary installed in Debian from one computer to another. I guess. -maarten