Hi Jörg,
> How would I mark a release for C5? > > Create a new release-info file and let the chicken core team add it to the CHICKEN 5 coop. I both in the same repo, eg nanomsg5.release-info for C5 and nanomsg.release-info for C4. > Any thought on how to have both a C4 and C5 version in the same repo? I'll > have to support C4 for quite a while. Now I wonder how best reorganize the > code to work for both. > I've kept C4 support by using cond-expand, like this <https://github.com/Adellica/chicken-nanomsg/blob/master/nanomsg-module.scm#L43-L46> : (import scheme) ;; make sure we have cond-expand (cond-expand (chicken-5 (import (chicken base) (chicken foreign))) (else (import chicken foreign))) > > * Observation: chicken-install does not install dependencies > > This is just odd: The .egg file contains (dependencies srfi-18); > chicken-install did the download but not install it. So compilation failed > until I manually did > > chicken-install srfi-18 > > That seems like a bug. No error messages after downloading? > * chicken-install -n -test > > Fails. One needs to actually install first, then run the test. > > Better at least warn that we test the installed version, not the > current one. (I recall this bite me before.) > > Best: just load the version from the working directory. > > Thanks for all the work which went into C5. > > /Jörg > > > _______________________________________________ > Chicken-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/chicken-users >
_______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
