---------- Forwarded message ----------
From: "Jeremy Steward" <xxxxxx@github.com>
Date: May 1, 2016 10:55 AM
Subject: [scheme-requests-for-implementation/srfi-113] CHICKEN Packaging (#3)
To: "scheme-requests-for-implementation/srfi-113" <srfi-113@noreply.github.com>
Cc:

This provides the legwork and files necessary to package SRFI-113 for CHICKEN Scheme, and incorporate it into an egg (CHICKEN Extension). Everything works without fail if you install locally, however as SRFI-128 is not yet packaged into an egg, the tool for testing installation (salmonella) will report failure. However, as I mentioned, if you install SRFI-128 locally and then call:

$ chicken-install -s -test

on this repository then you'll find it installs properly, the tests all run correctly, and you can import it from the REPL or compile against it using csc. On that note, originally this egg was to depend on SRFI-114: Comparators, however at John Cowan's request in #chicken on Freenode, I have transitioned it to use SRFI-128: Comparators (reduced). I believe 128 supersedes 114, as the code is cleaner and has tests, whereas SRFI-114 is in a bit of a mess (in my investigation SRFI-114 had some errors in the reference implementation itself, which I can provide details for if anyone is interested, however for the most part I think people will gravitate towards SRFI-128 instead).

NOTE: A LICENSE and README are added as well, to explain the licensing as well as what the extraneous files in the repository are if people come to visit the repo and wonder what the meta, setup, and release-info files are doing.

Lastly, if this is merged, could you please add a tag to the repo on Github so that we can include it as a CHICKEN extension? Should be as easy as:

$ git tag 0.1
$ git push origin master --tags

Whether you want to annotate that tag or not is up to you (-a option for git tag).


You can view, comment on, or merge this pull request online at:

  https://github.com/scheme-requests-for-implementation/srfi-113/pull/3

Commit Summary

File Changes

Patch Links:


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub