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.
On 12/7/06, Ivan Raikov <[EMAIL PROTECTED]> wrote:
Well, I am not the maintainer for the Debian Chicken package, so I
don't know. But unless the more recent versions of Chicken depend on
libraries or library versions that are not present in Debian, it's
probably not that difficult. Actually, the real problem here would be
that the Debian release cycle takes about a year, and once a Debian
stable release comes out, the packages in it may not be upgraded,
except for security-related patches. So whatever version of Chicken
you pick, you are stuck with it for a year -- which is not at all
unreasonable from a release manager's point of view. Debian stable is
"stable" because it provides a consistent and well-tested environment,
even if it doesn't have all the bleeding edge software. That's why I
think that if developers can rely on some support for older Chicken
releases, this will contribute greatly to the usefulness of Chicken
for software in mainstream Linux distributions.
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
