Re: Chicken-setup redesign (was: Re: [Chicken-users] Re: getopt, getopt_long?)

[felix winkelmann]

On Mon, Jul 14, 2008 at 2:35 PM, Mario Domenech Goulart
<address@hidden> wrote:
>>
>> Yes, that would work. You would also need a file for foo-1, I suppose,
>> if one wants to to load the highest minor version of 1.XXX. This will
>> produce lots of little loader-files, though.
>
> Hmmm.  I haven't thought about this level of granularity.  I thought
> users would either specify the exact version they want or no version
> (in this case, the highest would be used).  How would users specify
> they want to load the highest minor version of 1.XXXX?
>
> I was thinking about creating a little loader for the highest version
> _only_, for when users don't specify the version when loading an
> extension (so the highest is picked).
>
> For example, if the foo egg is installed (say its version is 1.0), the
> local repo would contain:
>
>    foo-1.0.so
>    foo.so
>
> foo.so would be generated by compiling
>
>   (require-library foo-1.0)
>
> since 1.0 is the highest version.
>
> Now suppose there's a new version for foo (1.1).  So, when foo is
> updated, the local repo would contain:
>
>    foo-1.0.so
>    foo-1.1.so
>    foo.so
>
> Now, foo.so would contain the code to load foo-1.1, not 1.0, but users
> will still be able to load 1.0 if they need (explicitly, though).
>

I guess having eitther the newest or a specific version is enough. I don't
think having finer grained access is really necessary, but I think Peter
proposed that?


cheers,
felix