Re: gnulib creates tests/ directory

2024-08-17 Thread Marc Nieper-Wißkirchen
Am Sa., 17. Aug. 2024 um 15:00 Uhr schrieb Bruno Haible : > Marc Nieper-Wißkirchen wrote: > > > This is fixed now. > > > > > > > What about the shell-based gnulib tool? Or should I consider that one > > deprecated? > > Yes. The shell-based implementation does not receive all bug-fixes and > improv

Re: gnulib creates tests/ directory

2024-08-17 Thread Bruno Haible
Marc Nieper-Wißkirchen wrote: > > This is fixed now. > > > > What about the shell-based gnulib tool? Or should I consider that one > deprecated? Yes. The shell-based implementation does not receive all bug-fixes and improvements any more, and is deprecated. Bruno

Re: gnulib creates tests/ directory

2024-08-17 Thread Bruno Haible
Simon Josefsson wrote: > > 'valgrindtests' would be a hack. > > How so? Because glueing together two words is not common in the English language. > However I also realize that the name is quite well established and has > been in the gnulib manual for a long time. Yes. > >> The naming was a cle

Re: gnulib creates tests/ directory

2024-08-17 Thread Marc Nieper-Wißkirchen
Hi! Bruno Haible schrieb am Sa., 17. Aug. 2024, 11:14: > Hi Simon, > > > Ouch. Shouldn't we rename 'valgrind-tests' instead? > > ... > > Whatever problem appears if we rename > > 'valgrind-tests' to, say, 'valgrindtests' we could fix. > > 'valgrindtests' would be a hack. > > 'valgrind-support-f

Re: gnulib creates tests/ directory

2024-08-17 Thread Simon Josefsson via Gnulib discussion list
Bruno Haible writes: > Hi Simon, > >> Ouch. Shouldn't we rename 'valgrind-tests' instead? >> ... >> Whatever problem appears if we rename >> 'valgrind-tests' to, say, 'valgrindtests' we could fix. > > 'valgrindtests' would be a hack. How so? The old name was a hack because it hijacked the *-te

Re: gnulib creates tests/ directory

2024-08-17 Thread Bruno Haible
Hi Simon, > Ouch. Shouldn't we rename 'valgrind-tests' instead? > ... > Whatever problem appears if we rename > 'valgrind-tests' to, say, 'valgrindtests' we could fix. 'valgrindtests' would be a hack. 'valgrind-support-for-tests' would have the same problem. 'test-support-with-valgrind' would

Re: gnulib creates tests/ directory

2024-08-17 Thread Simon Josefsson via Gnulib discussion list
Bruno Haible writes: > Hi Marc, > > Please keep the mailing list in CC. > >> > Does it still do so if you remove the 'valgrind-tests' modules from the >> > list? >> > >> >> It does not. > > OK, then the problem is that gnulib-tool does not know that 'valgrind-tests' > is special. Fixed like this

Re: gnulib creates tests/ directory

2024-08-16 Thread Marc Nieper-Wißkirchen
Hi Bruno, Am Fr., 16. Aug. 2024 um 18:03 Uhr schrieb Bruno Haible : > Hi Marc, > > Please keep the mailing list in CC. > This was due to my inability to use my email program properly. > > > Does it still do so if you remove the 'valgrind-tests' modules from the > > > list? > > > > > > > It doe

Re: gnulib creates tests/ directory

2024-08-16 Thread Bruno Haible
Hi Marc, Please keep the mailing list in CC. > > Does it still do so if you remove the 'valgrind-tests' modules from the > > list? > > > > It does not. OK, then the problem is that gnulib-tool does not know that 'valgrind-tests' is special. Fixed like this. We could have noticed the problem be

Re: gnulib creates tests/ directory

2024-08-16 Thread Bruno Haible
Hi Marc, > Although I don't use gnulib with '--with-tests', it does create a tests/ > directory during bootstrap and fills it with a few files. I attached my > gnulib-cache.m4. Does it still do so if you remove the 'valgrind-tests' modules from the list? Bruno

gnulib creates tests/ directory

2024-08-15 Thread Marc Nieper-Wißkirchen
Hi! Although I don't use gnulib with '--with-tests', it does create a tests/ directory during bootstrap and fills it with a few files. I attached my gnulib-cache.m4. Do you think I can prevent gnulib from creating the directory? Did I include some module that makes it create the directory, or d