Re: [Chicken-users] A question regarding "hidden" eggs

Hi Jörg, I think I may have bumped into similar needs now and again. I suppose one way of solving this is to clone the henrietta-cache and run this on your local server. However, I feel that's a little overkill if you just want a work-in-progress egg to be available with any chicken-install. I

Re: [Chicken-users] A question regarding "hidden" eggs

Am 20.01.2016 um 10:38 schrieb Kristian Lein-Mathisen: > Hi Jörg, > > I think I may have bumped into similar needs now and again. I suppose one > way of solving this is to clone the henrietta-cache and run this on your > local server. However, I feel that's a little overkill if you just want a >

Re: [Chicken-users] A question regarding "hidden" eggs

* Jörg F. Wittenberger [160116 19:35]: > Hi, > > I feel the need to have some space to stash away temporary glue code. > Is this about code you want to be able to chicken-install but noone else should see it? > Ideally the current version of it is always empty

Re: [Chicken-users] A question regarding "hidden" eggs

Am 18.01.2016 um 14:13 schrieb Christian Kellermann: > * Jörg F. Wittenberger [160116 19:35]: >> Hi, >> >> I feel the need to have some space to stash away temporary glue code. >> > > Is this about code you want to be able to chicken-install but noone > else

[Chicken-users] A question regarding "hidden" eggs

Hi, I feel the need to have some space to stash away temporary glue code. Ideally the current version of it is always empty and not of interest to anyone. As documentation always lags behind, it is empty with high probability. However development is not ideal. Not listing as in being marked