[1328] in athena10
Re: Metapackage rename
daemon@ATHENA.MIT.EDU (Anders Kaseorg)
Fri Mar 6 17:18:32 2009
Date: Fri, 6 Mar 2009 17:04:53 -0500 (EST)
From: Anders Kaseorg <andersk@MIT.EDU>
To: Jonathan Reed <jdreed@mit.edu>
cc: Evan Broder <broder@mit.edu>, debathena@mit.edu
In-Reply-To: <11CF34BC-5139-4042-B645-6249C4DF0F34@mit.edu>
Message-ID: <alpine.DEB.2.00.0903061648040.9996@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: 8bit
On Fri, 6 Mar 2009, Jonathan Reed wrote:
> debathena-standard -> debathena-basic
If we are going to rename debathena-standard, is it possible we can find a
name that, rather than implying some particular “level” of functionality,
substantively describes what kind of functionality that is?
(I don’t know if anyone would actually say
“I have plenty of bandwidth and disk space! Why would I only want the
basic edition?”
but that is the kind of connotation one gets from that name.)
I suggested “debathena-local” as one alternative.
> debathena-workstation -> debathena-graphical-login
I would maybe amend this to “debathena-login-graphical”, to follow the
convention of listing name components in order of increasing specificity.
As a side note, as we rename metapackages, we should remember to move them
from Section: debathena/base to Section: debathena/metapackages.
Anders