Email list hosting service & mailing list manager


Fwd: [scheme-requests-for-implementation/srfi-113] CHICKEN Packaging - version 0.3 (#5) Arthur A. Gleckler 05 May 2016 03:09 UTC

I have committed this change, tagged as requested.

— The Editor

Jeremy Steward <xxxxxx@github.com> writes:

| This is a quick patch to fix some issues regarding how the meta file
| and release-info are structured. The main problem, seen here, was that
| we were including more than just the files necessary to build the egg.
| This basically means stuff extraneous to the module itself (the HTML
| files, the tar.gz in the root of the repo) were getting pulled in even
| when users did not need them in order to install the egg.
>
| The files have been updated to reflect this change and now there
| should be no need to pull these files from Github every time a new
| release is made. If this is merged, could you add a tag called
| `CHICKEN-0.3' to the main repository?
>
| As always, thanks for any and all assistance you can provide. I
| understand I've made a lot of minor changes recently, however I
| believe this to be the last for a while, as I've gone to a thorough
| extent to test everything this time.
>
| ----------------------------------------------------------------------
>
| You can view, comment on, or merge this pull request online at:
>
| https://github.com/scheme-requests-for-implementation/srfi-113/pull/5
>
| Commit Summary
>
| * Updates meta, setup, and release-info verisons
| * Adds LICENSE and README (thought I did this)
| * Adds RC1 information
| * Changes old versions back to working state
| * Bumps rc number
| * Bumps rc number, fixes typo
| * Completes RC process for this branch
>
| File Changes
>
| * A LICENSE (19)
| * A README.md (31)
| * M srfi-113.meta (13)
| * M srfi-113.release-info (10)
| * M srfi-113.setup (2)
>
| Patch Links:
>
| * https://github.com/scheme-requests-for-implementation/srfi-113/pull/5.patch
>
| * https://github.com/scheme-requests-for-implementation/srfi-113/pull/5.diff
>
>
| —
| You are receiving this because you are subscribed to this thread.
| Reply to this email directly or view it on GitHub