Re: [Chicken-users] srfi-128 - almost

2018-08-20 Thread Mario Domenech Goulart
Hi Jörg, On 20 Aug 2018 19:24:28 +0200 Jörg F. Wittenberger wrote: > The release-info worried me too - TLD; super simple: if nothing else > changes, it should work as before. > > To add it to the C5 coop send a note to the list that >

Re: [Chicken-users] srfi-128 - almost

2018-08-20 Thread Mario Domenech Goulart
Hi Jörg, On 20 Aug 2018 19:33:24 +0200 Jörg F. Wittenberger wrote: > Thanks Mario, > > at the end of the day your suggestion will solve the development time > considerations I have. Except for the "check the download process" > part. > > Though actually rolling those out over a test network

Re: [Chicken-users] srfi-128 - almost

2018-08-20 Thread Jörg F . Wittenberger
Thanks Mario, at the end of the day your suggestion will solve the development time considerations I have. Except for the "check the download process" part. Though actually rolling those out over a test network looks like a bookkeeping hell. Brings me to a downside of C5 I'm seeing so far:

Re: [Chicken-users] srfi-128 - almost

2018-08-20 Thread Jörg F . Wittenberger
The release-info worried me too - TLD; super simple: if nothing else changes, it should work as before. To add it to the C5 coop send a note to the list that https://raw.githubusercontent.com/ThatGeoGuy/srfi-128/master/srfi-128.release-info it ready to go there. Best /Jörg On Aug 18 2018,

Re: [Chicken-users] srfi-128 - almost

2018-08-19 Thread Mario Domenech Goulart
Hi Jeremy, On Sat, 18 Aug 2018 15:55:36 -0600 Jeremy Steward wrote: > On 08/18/2018 06:12 AM, Jörg F. Wittenberger wrote: >> On Aug 18 2018, Jeremy Steward wrote: >> >>> Hey Joerg, >>> >>> I'm the maintainer for that egg. >> >> I know; we talked about that before as I had packaged the same srfi

Re: [Chicken-users] srfi-128 - almost

2018-08-18 Thread Jeremy Steward
On 08/18/2018 06:12 AM, Jörg F. Wittenberger wrote: On Aug 18 2018, Jeremy Steward wrote: Hey Joerg, I'm the maintainer for that egg. I know; we talked about that before as I had packaged the same srfi under the name of "comparators" before. Ah, right. Now I remember :) I'd be happy to

Re: [Chicken-users] srfi-128 - almost

2018-08-18 Thread Jörg F . Wittenberger
This looks pretty close. Where do I learn what I can put into setup.defaults? Looks like it could do the job I want. What I don't want: a local copy of the to-be-installed egg to begin with. What I want: chicken-install installing eggs almost like normal. For eggs being overwritten however,

Re: [Chicken-users] srfi-128 - almost

2018-08-18 Thread megane
Hi Jörg, Jörg F. Wittenberger writes: [...] > Brings back the question: how would I tell chicken to temporarily consult > other locations for egg distributions? E.g. I'd like to use chicken-install > in a fresh location outside the source directory of the egg to check that > the whole

Re: [Chicken-users] srfi-128 - almost

2018-08-18 Thread Jörg F . Wittenberger
On Aug 18 2018, Jeremy Steward wrote: Hey Joerg, I'm the maintainer for that egg. I know; we talked about that before as I had packaged the same srfi under the name of "comparators" before. I'd be happy to review the pull request, but just haven't had time. I can look it over tomorrow if

Re: [Chicken-users] srfi-128 - almost

2018-08-17 Thread Jeremy Steward
Hey Joerg, I'm the maintainer for that egg. I'd be happy to review the pull request, but just haven't had time. I can look it over tomorrow if necessary to get things merged in properly. Regards, On August 17, 2018 11:44:17 AM MDT, "Jörg F. Wittenberger" wrote: >Let's try an example. > >I

[Chicken-users] srfi-128 - almost

2018-08-17 Thread Jörg F . Wittenberger
Let's try an example. I forked the srfi-128 repo here and ported it to chicken 5 https://github.com/0-8-15/srfi-128 The .release-info still points upstream where the pull request went. This appears to install and work. Brings back the question: how would I tell chicken to temporarily consult