[147] in athena10
Re: Mananging an Athena 10 cluster software set
daemon@ATHENA.MIT.EDU (Timothy G Abbott)
Tue Apr 1 15:49:53 2008
Date: Tue, 1 Apr 2008 15:49:09 -0400 (EDT)
From: Timothy G Abbott <tabbott@MIT.EDU>
To: ghudson@mit.edu
cc: athena10@mit.edu
In-Reply-To: <200804011755.m31Htif9024960@outgoing.mit.edu>
Message-ID: <Pine.LNX.4.64L.0804011406420.23863@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Tue, 1 Apr 2008, ghudson@MIT.EDU wrote:
> The Athena 10 technical plan contains a number of plans like "ensure
> the native x3270 package is installed". I also have some requests
> from Alex Prengel for native software he'd like to see installed. I'd
> like to create the infrastructure to complete those items so we can
> knock them off quickly.
>
> My plan was to create a new equivs metapackage named
> debathena-cluster-software and make it depend on the Debian software
> packages we want installed on all cluster machines. (This is distinct
> from whatever metapackage will turn a machine into an Athena cluster
> machine with all of the self-maintenance features.) I am somewhat
> concerned about packages which don't exist in all suites; for
> instance, the sun-java6 packages exist in etch-backports but not in
> etch. This metapackage doesn't necessarily need to be installable on
> anything but Hardy, but if there's an easy way to make it installable
> everywhere (omitting software which doesn't exist for that suite), it
> might be nice.
>
Sounds reasonable.
One strategy for dealing with things like sun-java6 is to have the
dependency be "sun-java6 | sun-java5", which will require that they get
sun java, but on hardy will probably always get you java6. Another is to
use a Recommends: sun-java6 depencency which will do nothing (other than
upset aptitude) on etch but install the package on Hardy.
-Tim Abbott
