Re: [Chicken-users] New Eggs: SRFI-113 and SRFI-128

[Mario Domenech Goulart]

Hi Jeremy,

On Tue, 03 May 2016 08:40:48 +0200 Mario Domenech Goulart <address@hidden> 
wrote:

> On Mon, 2 May 2016 23:25:22 -0600 Jeremy Steward <address@hidden> wrote:
>
>> On 02/05/16 11:06 PM, Mario Domenech Goulart wrote:
>> | Some comments on the packaging:
>> |
>> | * (version ...) in .meta files is not used by chicken-install.
>> | Only the form in .setup is used.  I'd suggest removing (version
>> | ...) from .meta, otherwise people may start copy&paste'ing it, and
>> | we'll end up having one more file to update in case of version
>> | update (or one more place with inconsistent information, in case it
>> | is not properly update).
>>
>> Duly noted. I didn't think it was used, as I've never written it in
>> meta before; however, when I packaged SRFI-128 there was a version tag
>> in the meta file that already existed in the repo. In the future I
>> will not use them, in this case I opted to leave it as I did not want
>> to change too many things.
>>
>> |
>> | * instead of (author "foo, egg by bar"), you can use (author
>> | "foo") (maintainer "bar")
>>
>> This is interesting to know. I'll put it on the roadmap for future
>> versions. I can update them quite easily, however to actually put the
>> tag on Github requires me to message Arthur Gleckler (maintainer of
>> the scheme-requests-for-implementation account on Github), and ask him
>> to throw new versions up.
>>
>> |
>> | * Why do we have a tarball into the git repository?
>> |
>>
>> I do not know. You could do the same thing with a git tag, but for
>> some reason all the SRFIs on Github do this (so I presume there are
>> hysterical raisins of some kind behind this, potentially due to
>> mirrors that don't use git). I didn't include the tarball into the
>> meta file, so it shouldn't impact the egg.
>
> Ok.  Thanks for your comments, Jeremy.  I've added the eggs to the
> coop.  Thanks a lot for packaging them.

It turns out that the `files' form in .meta is not being used because
the .release-info file does not contain the `meta-file' directive, so
the whole repo is being added to the egg.  Can you please fix that?
More info at
http://wiki.call-cc.org/releasing-your-egg#meta-file-distribution

All the best.
Mario
-- 
http://parenteses.org/mario