On 3/24/26 15:08, Paul Eggert wrote:
On 3/24/26 09:46, Bruno Haible via Gnulib discussion list wrote:
museumware hardware or software does not have a high priority
Yes. That being said, if Dennis prepares a simple patch that does not
change the default timeout, but uses a longer timeout if (say)
MUSEUM_PIECE_TIMEOUT is defined to that longer value, that should
satisfy his needs without messing up Gnulib's CI builds, because then he
could build with -DMUSEUM_PIECE_TIMEOUT=100000 in his CFLAGS.
I am not sure if this is a joke or not.
I will make a patch but I suspect no one really cares about systems
still running from the 1990's. I even have a SPARCStation 20 here and
yes I also have multiple NVidia Quadro GPU stacked big x86 hardware
with silly amounts of ECC memory in them and ORACLE SPARC S7-2 also.
Also, the SiFive RISC-V stuff that is a joke in terms of performance.
So sure ... I can make a five line silly patch with -D_SLOW and no I
will not use the string "MUSEUM" unless you are putting me in there.
--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
