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 
 wrote:

> On Mon, 2 May 2016 23:25:22 -0600 Jeremy Steward  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'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

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

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

[Mario Domenech Goulart]

On Mon, 2 May 2016 23:25:22 -0600 Jeremy Steward  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'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.

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

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

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

[Jeremy Steward]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/05/16 11:06 PM, Mario Domenech Goulart wrote:
| Hello Jeremy, ...
|
| 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'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.

Thanks Mario.

- -- 
Jeremy Steward


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBAgAGBQJXKDZAAAoJEHVwwAZUeZnZ+54P/1G7KwvjWDoGE0287AYipadh
odtALHdS2FufEWmNS4Wuxx+0NGBbJyyQyRfqT2yco9lnytRE3BtXQYUxNeOrXf2p
1+3L7exUv/T2nKo+yrditj3liMXCl89FQqQCgzWsOQ8Y9KYw34Dpy0Ptfw29dKeu
Mr2KlErSkNOrh9d5q7FgOG3sExHJkBXy913QixzbEI5JQmGBDHifhdvP2ofDZ3mc
3VOr9HIJlgljKZUefcmXJ6JgiLy489rQ0SioNlg+w3xPSouUrdnu7v62tkdRPn0t
I+glObs1Fzn5GiYfFOyb+YFeTcupcK78gbUWopDk6Gcc61EApWQyfGjvbpDPhwh7
8CXWCmt6HfWzOqf3IjJIRpPodouM9CbfMxJ8C/HtUph3GpU3+bONkOu/j5lrYI/m
wkPBvODBP0if78cLV3iuWKPHQWBn86kYyD78bahHuDukpKTjw2DscuSU8+YmecNz
xNKCS5qZ1iQ2BiFRcfAEq1b7+nMrIeuVtgqpl6MMVziA3eoUpCjf3bb76+CVjBmy
2HEJ8mD8Wm5ZyTjGW9+ZD/ETtipmlGCCABMVR0jG5BPT3Fj/PxEbtTNaVHKgbowR
xIAvvbpqQ3VrHUOgPyCCkbJLcROvl2nCcKNNdE35akND9hYF6jAwVX/4Cmn9GAUd
BH6Atb30EIieA2QCA2fz
=R9SO
-END PGP SIGNATURE-

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

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

[Mario Domenech Goulart]

Hello Jeremy,

On Mon, 2 May 2016 22:37:12 -0600 Jeremy Steward  wrote:

> Over the weekend I've taken John Cowan's work on SRFI-113 (Sets and
> Bags) and SRFI-128 (Comparators (reduced)) and packaged them up nicely
> into eggs. The URLs are below, I think it'd be great if we could add
> them to the coop. Salmonella reports all tests passing and
> installation working correctly, with one caveat: Since SRFI-113
> depends on SRFI-128, I cannot yet run Salmonella independently on
> SRFI-113, however I expect there to be no errors.
>
> https://github.com/scheme-requests-for-implementation/srfi-113
> https://github.com/scheme-requests-for-implementation/srfi-128
>
> I plan to package SRFI-133 (Vector Library (R7RS-compatible)),
> SRFI-121 (Generators), and SRFI-127 (Lazy Sequences) as time permits
> over the next couple of weeks. Any feedback into which (if any) new
> SRFI's that haven't been packaged for CHICKEN are desired would be
> great, so I can focus on those additionally, provided the work isn't
> too severe.

Thanks a lot.

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'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).

* instead of (author "foo, egg by bar"), you can use (author "foo")
  (maintainer "bar")

* Why do we have a tarball into the git repository?

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

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

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

[Jeremy Steward]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello all,

Over the weekend I've taken John Cowan's work on SRFI-113 (Sets and
Bags) and SRFI-128 (Comparators (reduced)) and packaged them up nicely
into eggs. The URLs are below, I think it'd be great if we could add
them to the coop. Salmonella reports all tests passing and
installation working correctly, with one caveat: Since SRFI-113
depends on SRFI-128, I cannot yet run Salmonella independently on
SRFI-113, however I expect there to be no errors.

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

I plan to package SRFI-133 (Vector Library (R7RS-compatible)),
SRFI-121 (Generators), and SRFI-127 (Lazy Sequences) as time permits
over the next couple of weeks. Any feedback into which (if any) new
SRFI's that haven't been packaged for CHICKEN are desired would be
great, so I can focus on those additionally, provided the work isn't
too severe.

Best regards, and thanks again to the work that John Cowan, Arthur
Gleckler, and the SRFI committee has put in to make these libraries
possible.
- -- 
Jeremy Steward


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBAgAGBQJXKCr3AAoJEHVwwAZUeZnZJRIP/R8ftcRC595P6uZY4rIqWdUc
gGHx093YcCaKFZNkflAtQs8KoSZZQVBw5ZsfZ9q/r+/P2CvsHtlzy+bAIe8agMP8
YtNFxyQgNKtHfaDPw0YRLiJOZOJlQWAO4Kdo6mOLI4cxrZH+PPs765UdpC37NDNp
57zdnKfS+vvg/LiNKPVeAvQHKOSoCRObiwdnvWA6yQLYMsWjQoIqFMDYAUvwr2YA
luJlY0QaH1CDmGhYs3NdthUo8Lehx4k3Isw9bAJlxr/IQzortxZLuVHsrSbGbKAY
rzYiOgblZtkdQTOB4sBeYRe3U157Lq32EsysLWsIL22FcJjSFIC2bw/cGZZ0HWNr
eZ9WEm8++1a9jjIFmBZConE8zETEn4YdJoIbva6pX1XDlHhbw910PGEZJ7OyBvxw
274MMV69gbZgcm1qClhu81vtL+xIGkDWYYoy+iIVX7EvEKiJf67M5jfBECItzeQN
m7SiJxnGwX++dYLZK5tvZsrABJ0w/M3NjyrDFOXMvqNIzJxFAMthqsJYcPAa7k7e
d1N4/i45Az42xrZGtumUOKL9WhvE859tXQwPI6fk7wI6bEUbkyQqeeE5U/nWMcj4
Y8Ij3xI/6ftXJZFXC1+8RrAgAxBPCFyp8vHELuntvqSFNfXHB8LCYjGtMObG2TaP
3cYN0uuWMGzXJj74ElBg
=6Qog
-END PGP SIGNATURE-

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users