Re: [Chicken-users] New Eggs: SRFI-121, SRFI-127, SRFI-133

2016-07-24 Thread Mario Domenech Goulart 
Hi Jeremy,

On Sun, 24 Jul 2016 09:18:54 -0600 Jeremy Steward  wrote:

> On 07/24/2016 05:59 AM, Peter Bex wrote:
> | On Sun, Jul 24, 2016 at 01:28:25PM +0200, Mario Domenech Goulart
> | wrote: Hi Jeremy,
> |
> |> The repositories can be found below:
> |>
> |> https://github.com/scheme-requests-for-implementation/srfi-121
> |> https://github.com/scheme-requests-for-implementation/srfi-127
> |
> | Installation of srfi-127 fails because "lseqs/lseqs-impl.scm" is
> | referenced but it is not in the list of files to be fetched (it is
> | in the repository, but not listed in .meta's `files').
> |
> | Error: (open-input-file) cannot open file - No such file or
> | directory: "lseqs/lseqs-impl.scm"
>
> Ah! Curses, this was the third one I did yesterday, so I can see why I
> messed it up. I fixed the typo in .meta and submitted a PR to the
> repo. If you try again in a few hours (maybe tomorrow at latest) I
> suspect it will have been merged and the egg can be added successfully.

Ok.  I made a little tool to test new eggs.  You can find it here:
https://github.com/mario-goulart/test-new-egg

This tool combines henrietta-cache and salmonella in the same tool, so
both .release-info files and eggs themselves can be tested before being
published.

To use it, chicken-install it and run:

  $ test-new-egg 

Where  is the URI that points to the raw .release-info file.

P.S.: have you noticed my comment on dynld-name in .setup files?

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-121, SRFI-127, SRFI-133

2016-07-24 Thread Jeremy Steward 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 07/24/2016 05:59 AM, Peter Bex wrote:
| On Sun, Jul 24, 2016 at 01:28:25PM +0200, Mario Domenech Goulart
| wrote: Hi Jeremy,
|
|> The repositories can be found below:
|>
|> https://github.com/scheme-requests-for-implementation/srfi-121
|> https://github.com/scheme-requests-for-implementation/srfi-127
|
| Installation of srfi-127 fails because "lseqs/lseqs-impl.scm" is
| referenced but it is not in the list of files to be fetched (it is
| in the repository, but not listed in .meta's `files').
|
| Error: (open-input-file) cannot open file - No such file or
| directory: "lseqs/lseqs-impl.scm"

Ah! Curses, this was the third one I did yesterday, so I can see why I
messed it up. I fixed the typo in .meta and submitted a PR to the
repo. If you try again in a few hours (maybe tomorrow at latest) I
suspect it will have been merged and the egg can be added successfully.

| Generally speaking, I would avoid using "meta-file" as a
| distribution mechanism, precisely for this reason: it's too easy to
| forget adding particular files.  The targz distribution method
| works fine with GitHub.

Well, yes. I originally packaged SRFI 116/117/113/128 using the targz
method, but the SRFI editors add some extraneous files to the
repository (strangely enough, a targz of the entire repo is... in the
repo). In any case, rather than have users download a few extra MB of
extra files, I think this works better.

| We talked on IRC about using meta-file, but that was in an attempt
| to avoid forking the upstream eggs, but that didn't work out.

I do recall some discussion along these lines. However, here it's not
to avoid forking, but rather to avoid downloading files that might
pertain to other scheme distributions or may be unnecessary to provide
through `chicken-install` (the targz in the repo as the prime example).

- -- 
Jeremy Steward


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXlNxYAAoJEKflx7ZMcbY7CbAP/AqXypXOord2IQqar3IgFbbG
UL+huDfVAGVgMEwphmckCyV/xmskTgdZFckymlp2VWmo7At8zCVsJjaDkTEQRIl9
4fXNAhttAGG4LT1KGyRJ894Up2kApEJulefZha2M8PpZMwpoOR/baHVtf6efeSHe
4oBE1RRi5As1nu/dmLfxN3W88swhxKsSKSeqfGabppYvhAjV9x7v/8/Bah4iYVgF
IkxFAxksUWyxCxuK+KOVn1qQlcwAny+mo2PMrW6jTLHtNhGKe26KRL39WHS0DAm9
eiluHe5/uLCvJrzD9XwA7d3TA9BilXIwxtCsQfB1u2q9IbOGITfPLetrKVcywMMk
Yig45DHOnTWbaYjmO4YJmJb2tUsnTNkLXcnZVQKRP2q0GI0IJbLRtxKfDD6cwqaV
XlzGpn3EsIe/s9odJXqWOmWbtQ221003nHefVOABkGQzPyTB6XLuupyqEvfxDKOf
PvvE+ky33eoZVQbjBRhLkqkebBuc79xGQjltjJ1NM+DqoHns+wDy/0w9uOvhb51m
dXG1uqiMFvibkFkwslezSDD3X+3tX5UK5N49Tc7RwEcsy2lEUTVpWFQ72srPFIjM
IBPZinHs0ARqvXp8WkKFmB0AzdG3CigvteEQ6fLmi7BiUCCJZRUoi2fwX0ImsRhu
1t4rFWD1pZ2vp5i2ba2C
=3SyJ
-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-121, SRFI-127, SRFI-133

2016-07-24 Thread Peter Bex 
On Sun, Jul 24, 2016 at 01:28:25PM +0200, Mario Domenech Goulart wrote:
> Hi Jeremy,
>
> > The repositories can be found below:
> >
> > https://github.com/scheme-requests-for-implementation/srfi-121
> > https://github.com/scheme-requests-for-implementation/srfi-127
> 
> Installation of srfi-127 fails because "lseqs/lseqs-impl.scm" is
> referenced but it is not in the list of files to be fetched (it is in
> the repository, but not listed in .meta's `files').
> 
> Error: (open-input-file) cannot open file - No such file or directory: 
> "lseqs/lseqs-impl.scm"

Generally speaking, I would avoid using "meta-file" as a distribution
mechanism, precisely for this reason: it's too easy to forget adding
particular files.  The targz distribution method works fine with GitHub.

We talked on IRC about using meta-file, but that was in an attempt to
avoid forking the upstream eggs, but that didn't work out.

Cheers,
Peter


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

Re: [Chicken-users] New Eggs: SRFI-121, SRFI-127, SRFI-133

2016-07-24 Thread Mario Domenech Goulart 
Hi Jeremy,

On Sat, 23 Jul 2016 15:03:48 -0600 Jeremy Steward  wrote:

> I've taken the opportunity to package SRFI-121 (Generators), SRFI-127
> (Lazy Sequences), and SRFI-133 (Vectors [R7RS-compatible]) for
> CHICKEN. The eggs all pass salmonella and shouldn't contain any
> errors.

Thanks a lot for the new eggs.  Please, see some comments below.

> The repositories can be found below:
>
> https://github.com/scheme-requests-for-implementation/srfi-121
> https://github.com/scheme-requests-for-implementation/srfi-127

Installation of srfi-127 fails because "lseqs/lseqs-impl.scm" is
referenced but it is not in the list of files to be fetched (it is in
the repository, but not listed in .meta's `files').

Error: (open-input-file) cannot open file - No such file or directory: 
"lseqs/lseqs-impl.scm"

> https://github.com/scheme-requests-for-implementation/srfi-133
>
...
>
> Cheers, and let me know if (when?) you find any bugs, either in the
> installation / setup or otherwise.

Note that all .setup files install (dynld-name "file-without-extension"), 
but the compiler output is written to files with .so extension
(hardcoded).

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-121, SRFI-127, SRFI-133

2016-07-23 Thread Jeremy Steward 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello all,

I've taken the opportunity to package SRFI-121 (Generators), SRFI-127
(Lazy Sequences), and SRFI-133 (Vectors [R7RS-compatible]) for
CHICKEN. The eggs all pass salmonella and shouldn't contain any
errors. The repositories can be found below:

https://github.com/scheme-requests-for-implementation/srfi-121
https://github.com/scheme-requests-for-implementation/srfi-127
https://github.com/scheme-requests-for-implementation/srfi-133

Thanks again to John Cowan, Arthur Gleckler, and the SRFI committee
for the reference implementations of these libraries. For those who
don't know, these three libraries were recently voted in to be
included as part of R7RS-large. While I don't think that CHICKEN
strives for R7RS-large compatibility, having these libraries working
with CHICKEN is a pretty good step towards making R7RS compatibility a
trivial effort.

Cheers, and let me know if (when?) you find any bugs, either in the
installation / setup or otherwise.
- -- 
Jeremy Steward


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXk9uvAAoJEKflx7ZMcbY7GCcP/3d3znISeSj/V6rOxTqQYamJ
7ElFkGwVfXYlI3AysBENPT2La4li2OYKEdRZPufxs7PCALBIWCX6DsmAGDKWvJZK
2FVpwYJ5ryooRBvl6lMt6wIOao8+69T4UDCaRYG9SkcHh8Y8q0h/TwHmKzqtHr0R
w/totVBV32V6ESrnvgpx9KYEvdYEY6EpN2D7GQ2ncSuZZkMHi1CZq25JW6VlxPUG
cCnvgLznULduf9unEvy/sN71kPLTTLiR6rEzJhX3kDgdnQlJx8VKkfaeyFGHqJX3
HKLtcCduIsiEXaJdh8AKHa0VxGMHLQZLnE7C2aoiDnMSXEXXQSH/6lgKZRb+Em4a
ZvBTrFCuS2KYXxMoTB18jLK4pa++VsvK40CQS3CxaMywpa3ty2Y8iCN/+iUychfV
/EqGDZI3I3Qy7tXcIfCrOEzmC8Ksrt0YmV6w3Mppa+yZXTM2NE4FhXGfj8p5kGZU
u7azPsQZajRHpakUd+VauT0hHTdmLlBXXGbSKwQBsfBvCkdgOrl1seAyMfYIAQIE
okskxuxtoNY3ZRG1a/uibMhQ+SeXxo5Jg8kLjfGakaM5XeutHrUXtHEtkNK6AcmJ
Z52O6ctENBblt/2v0LUDQmyvFJkI0h7M6Xi1lczL85RKzS0xVlUb2rCPQJCvNUGy
Fzjw2KSmEUoME8H1dzGT
=kspH
-END PGP SIGNATURE-

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