[609] in athena10
locker software and 'debathena-cluster-software'
daemon@ATHENA.MIT.EDU (Greg Price)
Fri Nov 7 20:30:08 2008
Date: Fri, 7 Nov 2008 20:25:18 -0500
From: Greg Price <price@MIT.EDU>
To: athena10@mit.edu
Message-ID: <20081108012517.GJ20760@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
The infoagents locker grew an arch/i386_deb40 directory this week. I
noticed because my mail client threw an error when trying to show me
an HTML message, because I have /mit/infoagents/bin/lynx in my mailcap.
Meanwhile it looks like 'lynx' was added to debathena-cluster-software
in 0.5.2, r23240, the next day.
From discussions here, it looks like we'll be taking a lot of locker
software this way. For the reasons discussed I think that's right.
But Athena isn't just cluster machines, so we should be sure to keep
this functionality available on Athena outside clusters. We've been
calling the package 'debathena-cluster-software', but I think we
should think of it as a generic 'batteries included' package,
supplying all the ancillary software users expect on a fully-powered
Athena workstation.
E.g., we should aim for this package now called debathena-cluster-software
to be installed on dorm-owned workstations, SIPB office heads, etc.
This suggests two things:
- rename the package to reflect that intent; someone suggested
debathena-third-party, or a more apt name might be
debathena-extra-software;
- for those of us who care about Debathena not on Hardy, we should
maintain debathena-cluster-software for other distributions;
e.g. on etch it conflicts with debathena-workstation just now
over the gaim->pidgin rename;
- those of us who maintain Debathena workstations, say SIPB office
heads, should install debathena-cluster-software and try to get
all the general-purpose software we need into that package;
How does this approach sound to everyone else?
Greg
