Re: [Chicken-users] Wish list

[Christian Kellermann]

* Aleksej Saushev <address@hidden> [130210 22:08]:
>   Hello,
> 
> Mario Domenech Goulart <address@hidden> writes:
> 
> > On Sun, 10 Feb 2013 22:36:41 +0400 Aleksej Saushev <address@hidden> wrote:
> >
> >> I have talked to a user, and he reminded me of my past experience of
> >> using Chicken in production environment around four years ago. While
> >> many things improved since then, there're still some I'd like to have.
> >>
> >> 1. Distribute eggs by HTTP(S) and/or FTP(S).
> >>
> >> Today I have "chicken-install -r", but it still is a specialized client.
> >> I don't quite understand what I can do if I'm in mildly hostile network
> >> where automatically configured proxy requires authentication mechanism
> >> chicken-install doesn't support.
> >
> > Most (if not all) eggs are available via HTTP(S).  For eggs hosted on
> > call-cc.org, you ca use
> > https://code.call-cc.org/svn/chicken-eggs/release/4/
> 
> I have just tried it. It has asked user name and password.
> It seems not to allow anonymous access. This is not what I wish, I think.

User: anonymous, password is empty ("").

> 
> > The other hosts (github, bitbucket, gitorious etc) also provide HTTP(S)
> > access (including tarballs).
> >
> >
> >> 2. Distribute eggs as source tarballs.
> >>
> >> In addition to (1) it would be nice if eggs were distributed as tarballs
> >> rather than individual files. In addition, such tarballs could be
> >> accompanied by cryptographic hash sums (individually per egg or as big
> >> list for the whole repository). These tarballs could even be signed, even.
> >
> > Yeah, that can be a handy feature for packagers.
> >
> > Maybe that feature can be implemented via some henrietta-cache hook or
> > something?
> 
> By the way, what I wish is more than tarball automatically generated at
> each request. I want it stable, so that I could record cryptographic sums
> and be sure that the archive doesn't change tomorrow without version change.
> This is different from what github does (I don't know about bitbucket
> and the rest).

Henrietta cache does check each source specified in the egg-locations
file every hour for new releases, then downloads the source tarballs
for these and chicken-install will rely on these stored tarballs.
These are not created on the fly, so what you are suggesting could
be done this way. Or am I missing something?

Kind regards,

Christian

-- 
In the world, there is nothing more submissive and weak than
water. Yet for attacking that which is hard and strong, nothing can
surpass it. --- Lao Tzu