On 12/1/25 15:21, Mario Domenech Goulart via Chicken-users wrote:
That's strange. On Linux and FreeBSD, the egg passes 'test-new-egg'
with no problerms. (This is after uninstalling locally installed
srfi-128 and srfi-162.) In both OS using latest chicken (rev
224e7aa3).
So I don't understand why the above failures occurred. Appreciate any
insights you could share.
Thanks for the details. I was using 44df27bb of chicken-core. I've
updated it to the latest state (224e7aa347) and now test-new-egg passes.
To be honest, I don't know exactly which change ended up fixing the
issue.
That said,
https://codeberg.org/jrapdx/srfi-162/src/tag/0.1.0/tests/run.scm#L8-L13
looks particularly strange.
There was a similar problem with the SRFI-128 egg which needed a few
commits in order to work. I believe the fixes were 3c719f69 and
2b0ba37a, which more or less were broken on the SRFI-128 egg as well,
and for the same reasons.
Separate from that: A question for jrapdx— does (srfi 162) export a
second module (srfi 128) directly? As the maintainer for SRFI 128 I am
wondering if it is worthwhile to maintain separate code here or whether
it makes more sense to expect eggs to transition to 162 in the future.
Given I've already done most of the work to get SRFI-128 in order for
C6, it isn't really a problem (and will make other ports easier), but
may be worth noting for visibility.
Cheers,
--
Jeremy Steward
