Re: [Chicken-users] Wish list

[Matt Gushee]

Hi--

On Sun, Feb 10, 2013 at 12:55 PM, Mario Domenech Goulart <address@hidden> wrote:

On Sun, 10 Feb 2013 22:36:41 +0400 Aleksej Saushev <address@hidden> wrote:

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/

The other hosts (github, bitbucket, gitorious etc) also provide HTTP(S)
access (including tarballs).

 

Is there a straightforward way for a user to *choose* HTTPS when installing an egg? I thought the -transport option might do that, but according to the manual, that is not the case.

 

> 3. Label eggs with their versions.

>
> It is unfortunate, that chicken-install still doesn't report egg version
> in any way. Did I overlook it? It would be nice, if eggs would follow
> common standard (eggname-x.y.z.tar.gz containing subdirectory eggname-x.y.z).

You can install specific egg versions by specifying them like this:
<egg>:<version>.  Example

   $ chicken-install sendfile:1.7.23

That's a useful feature that I was unaware of. I think it would also be useful if the -list option showed version information.

 

> 4. Support installation of eggs into directory other than
> $(chicken-install -repository).
>
> It would be nice to be able to install eggs into private area
> (for testing purposes, for migration purposes, just as developer
> convenience, whatever).

As far as I understand what you mean, that's already supported.  See
http://wiki.call-cc.org/man/4/Extensions#changing-repository-location

But it seems to me that the issue here is not only where the eggs are installed, but where [csi|csc] looks for them at [runtime|compile time]. As I understand it the repository path is *one* location in the filesystem. It might be nice to support multiple paths.

--

Matt Gushee