Re: [Chicken-users] New user; egg problems

[Ivan Raikov]

  You make a good point; actually, I would say that Debian needs to
have a package for each individual egg, so that the developer who
wishes to release Debian packages of their Chicken code can have
precise control over dependencies. But then this means that the egg
repository must match egg versions with Chicken versions, which is
essentially what I'd like to have. I am not suggesting that each egg
developer test their egg with all versions of Chicken ever
released. All I am proposing is a field in the egg setup file that
indicates which version(s) of Chicken was/were used to compile and
test that egg. This could be combined with a unit test framework. Such
a system would be optional, but it would still allow for dedicated
developers to port the eggs they are interested in to Debian stable
and package up their software.


     -Ivan

Zbigniew <address@hidden> writes:

> It seems to me that if Debian provides a Chicken 2.3 package for
> stability reasons, then Debian should also provide a 2.3 eggs package
> and keep it up to date.  Using chicken-setup is inherently "unstable"
> from the perspective of Debian stable, since the eggs are constantly
> updated and haven't gone through the Debian release cycle.  If you
> care enough to run Debian stable, you don't want to do this.  If you
> want to use chicken-setup, you should use the latest stable version of
> Chicken, which to me implies compiling or using Debian unstable (if
> available).
>
> I know that seems Draconian, but getting eggs to work on earlier
> versions of Chicken is not always easy.  Dependencies may change,
> features may not be available, etc.  I think it would be a massive
> pain to maintain such a thing, not to mention the infrastructure isn't
> there, although Felix can be surprising.
>