Re: 1.16.90 regression: configure now takes 7 seconds to start

2024-06-12 Thread Simon Richter
Hi, On 6/13/24 10:44, Jacob Bachmeyer wrote: Second, because timestamp resolution is actually per-volume, which in the POSIX model, means it varies by directory.  You can even have a modern filesystem (with nanosecond granularity) mounted on a directory in a FAT filesystem (with two second gr

Re: improved timestamp resolution test (was: 1.16.90 regression: configure now takes 7 seconds to start)

2024-06-12 Thread Jacob Bachmeyer
Karl Berry wrote: Does BSD ls(1) support "--time=ctime --time-style=full-iso"? BSD ls does not support any --longopts. Looking at the man page, I don't see "millisecond" or "subsecond" etc. mentioned, though I could easily be missing it. E.g., https://man.freebsd.org/cgi/man.cgi?ls Even

Re: 1.16.90 regression: configure now takes 7 seconds to start

2024-06-12 Thread Jacob Bachmeyer
dherr...@tentpost.com wrote: At some point, it becomes unreasonable to burden common platforms with delays that only support relatively obscure and obsolete platforms. Configure scripts already have a bad reputation for wasting time. Even if they are faster than editing a custom makefile, the

Re: Bug Resilience Program of German Sovereign Tech Fund

2024-06-12 Thread Jacob Bachmeyer
Karl Berry wrote: [...] > and reduce technical debt. I don't know what that means. I instinctively shy away from such vague buzzwords. Essentially, "technical debt" means "stuff on the TODO list" and more specifically the accumulation of "good enough for now; fix it later" that tend

Re: 1.16.90 regression: configure now takes 7 seconds to start

2024-06-12 Thread Karl Berry
Does BSD ls(1) support "--time=ctime --time-style=full-iso"? BSD ls does not support any --longopts. Looking at the man page, I don't see "millisecond" or "subsecond" etc. mentioned, though I could easily be missing it. E.g., https://man.freebsd.org/cgi/man.cgi?ls Even if there is such an

Re: 1.16.90 regression: configure now takes 7 seconds to start

2024-06-12 Thread Karl Berry
It should save 6 seconds. Because it goes like this: - Test whether 0.01 sec works. - Test whether 0.1 sec works. - If not, set the variable to 2, because that's the worst case and it *must* work. At which places will then a 'sleep 2' be done where (if not VFAT) a

Re: 1.16.90 regression: configure now takes 7 seconds to start

2024-06-12 Thread Karl Berry
> Any other ideas? A horrible one: :) split the test so it can be performed in parallel with others -- upper half starts the sleep in the background, lower half waits for it to complete. No thanks. I can't even begin to imagine the portability and edge case problems that w

Re: Bug Resilience Program of German Sovereign Tech Fund

2024-06-12 Thread Christoph Grüninger
Hi Karl, thanks for the detailed answer! I resonate with your concerns. I will only apply if you and others like Zack and Paul agree. Either say no or please provide feedback to my proposed text for the program application. If that means providing patches for open bugs, then great. That is wh

Re: Bug Resilience Program of German Sovereign Tech Fund

2024-06-12 Thread Christoph Grüninger
Hi Paul, while I wish that there would be better options, this seems to me the most fitting open source support program for Automake & Autoconf I have came across in the last decade. To me, the prospect is much brighter. If people learn Autotools, they face difficulties, which they may address

Re: 1.16.90 regression: configure now takes 7 seconds to start

2024-06-12 Thread Zack Weinberg
On Tue, Jun 11, 2024, at 7:00 PM, Karl Berry wrote: > Maybe this is a silly question, but, is there a reason why this test > needs to be performed in every single package that uses Automake? > > I was under the impression that the purpose of this test was > merely to speed up running Automa