[1212] in athena10

home help back first fref pref prev next nref lref last post

Re: Building our own mit-scheme

daemon@ATHENA.MIT.EDU (Evan Broder)
Tue Feb 24 20:22:55 2009

Message-ID: <49A49D33.1080100@mit.edu>
Date: Tue, 24 Feb 2009 20:21:55 -0500
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: Anders Kaseorg <andersk@mit.edu>
CC: Geoffrey Thomas <geofft@mit.edu>, debathena@mit.edu
In-Reply-To: <alpine.DEB.2.00.0902241957350.3830@vinegar-pot.mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

I agree with everyone else on this one, in terms of how the Debathena
repository should be used. In particular, there are other Schemes that
work fine, and Athena 10 won't even ship on Intrepid (except for early,
but whatever).

I'm skeptical about getting this fixed in intrepid-updates, since I'm
skeptical that we can or want to come up with the minimal patch, and
that's a pretty strong requirement. I'd recommend fixing this in Jaunty
(since the package is completely disfunctional, it should be easy to get
a freeze exception), and then using intrepid-backports if you really care.

- Evan

Anders Kaseorg wrote:
> Trying to fix Intrepid bugs in our repository is a mistake.  That is
> not what the Debathena repository is for.  We really want the fixes to
> go upstream.
>
> mit-scheme has never been locally installed on Athena, so this is not
> even a feature that is important for Athena 10.  People that need it
> in the mean time can run it from the scheme locker like they did before.
>
> I think it would be great to have a _separate_ repository that
> contains “cool SIPB packages”, analagous to the outland locker and/or
> the sipb locker, but this is not something that we should force on
> every Debathena user.
>
> Anders

home help back first fref pref prev next nref lref last post