On 2018-08-25 14:01, Jörg F. Wittenberger wrote:
> Maybe it makes more sense to have the -n switch only in effect for the egg
> in the current directory while still installing dependencies.
That makes sense to me.
In the case where people don't want dependencies to be installed either,
they can
Jörg F. Wittenberger wrote:
> Apparently chicken-install passes the -n switch down to the dependencies it
> need to install.
I reported the same thing on IRC today. I think it makes sense and would like
to have a switch that instructs chicken-install to *only* build, and install if
-n is
not
Hi all,
in the meantime I understood why chicken-install would not install
dependencies:
chicken-install -n
While messing around I did not want the egg in the current directory to be
installed. Just the dependencies.
Apparently chicken-install passes the -n switch down to the
Thanks Mario and Kristian for your responses.
On Aug 17 2018, Mario Domenech Goulart wrote:
I'm maintaining all my eggs in the same repo, same branch, same
.release-info file and same versioning scheme for both CHICKEN 4 and 5.
That's what I'd want.
In my experience, that's not difficult.
Hi Jörg,
On 17 Aug 2018 12:33:28 +0200 Jörg F. Wittenberger
wrote:
> I just ported a first egg. (Pigeon-hole, "simple" mailbox with
> capacity constraint flow control and no timeouts.)
>
> * Question: what's about the .release-info
>
> This https://wiki.call-cc.org/porting-c4-to-c5 was
Hi Jörg,
> How would I mark a release for C5?
>
>
Create a new release-info file and let the chicken core team add it to the
CHICKEN 5 coop.
I both in the same repo, eg nanomsg5.release-info for C5 and
nanomsg.release-info for C4.
> Any thought on how to have both a C4 and C5 version in the
