Hi Bruno, On 3/21/24 8:45 AM, Bruno Haible wrote: > Oh, indeed, the unit test works in the directory in which I committed it, > but does not work in a fresh git checkout :-( The .gitignore files > cause a lot of trouble. But it should be fixed by now.
Thanks! I see you also fixed the 'autom4te.cache' and '.deps' issues as well. I noticed those after my original email... I also noticed you added import-tests/README. It might be worth adding GNU Bison as a test case. It has not had a commit since Nov 4 2022, but builds fine running: $ git submodule update --init $ env GNULIB_TOOL_IMPL=sh ./bootstrap $ ./configure $ make all But the Python version will fail to run 'make all' due to missing PO files. The test case would help fix that. It also uses --automake-subdir-tests which I don't think our current test cases cover. If I remember correctly, that option was added for Bison so I am not sure if other packages even use it. > Regarding not "littering" it: The usual rules for saving space in a > git repository apply: > ... > The current size, 300 MB, is not something we want every gnulib _user_ > to download. But every gnulib _developer_, that's OK. Okay, that sounds good to me. I am slightly *too* careful when it comes to saving space, out of habit. Sometime in the past decade, U.S. (maybe just California?) ISPs decided that everyone needs data caps. :( I ended up forking over extra money, but the habit remains. Collin
