[349] in athena10
Adding software "to the release"
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Wed Jul 30 10:21:37 2008
Message-Id: <AFE7CAC0-731B-4712-A99B-B932EB92B319@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: athena10@mit.edu
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Jul 2008 10:20:57 -0400
So, Alex and I have been talking a bit about how the way we deal with
3partysw (particularly GPL'd packages) is likely to change in Athena
10. My understand at the moment is that lockers we previously copied
locally (Acrobat, Ooffice) will have their equivalent packages
installed from universe by debathena-workstation (and possibly -
standard).
I'm still coming up to speed on how Debian handles packaging and
requirements, so my question at this point is: how easy or hard is it
to decide that a new piece of software should be installed as part of
"Athena"? That is, how much lead time is required, and how would
machines receive the new package? I assume it's not a lot of effort,
I just want to make sure I have my facts straight before I move
forward on working with Bill and Alex for some guidelines for 3rd
party software on Athena 10.
-Jon
