[540] in athena10
Re: cluster-software install problem analysis
daemon@ATHENA.MIT.EDU (William Cattey)
Tue Sep 23 13:58:50 2008
In-Reply-To: <alpine.DEB.2.00.0809231333360.32305@vinegar-pot.mit.edu>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <AD0DDB75-08D9-40A9-AB91-67A06AF924F4@mit.edu>
Cc: Tim Abbott <tabbott@mit.edu>, Greg Hudson <ghudson@mit.edu>
Content-Transfer-Encoding: 7bit
From: William Cattey <wdc@MIT.EDU>
Date: Tue, 23 Sep 2008 13:56:22 -0400
To: athena10@mit.edu
I found the question, "Will this machine be used for Athena
development?" to be a bit confusing. In fact, the first time I read
the question, I understood it as Greg put it in his reply, "Will this
machine be used for development?"
In retrospect, it was not asking me if I wanted the C compiler et. al.
It was asking me if I was going to build debathena packages. Right?
I wonder if we want debathena developers to have to read a document
that explains the various conventions and best practices, and in THAT
document to give the name of the package to install that contains the
stuff to build debathena packages. Then it's no longer a matter of
choosing whether the stuff is in Workstation or Cluster, and a
potentially confusing question gets to be removed from the installer.
But I'm still a real newbie with regards to debathena, so I may have
missed the point.
-wdc
On Sep 23, 2008, at 1:44 PM, Tim Abbott wrote:
> On Tue, 23 Sep 2008, Greg Hudson wrote:
>
>> On Tue, 2008-09-23 at 13:29 -0400, Tim Abbott wrote:
>>> Is the intention that cluster machines will have debathena-build-
>>> depends
>>> installed?
>>
>> Yes.
>>
>> So in this proposal, the debathena-build-depends dependency would
>> move
>> from workstation to cluster.
>
> By cluster, do you mean cluster-software?
>
> I agree -workstation is a weird place for -build-depends. I think
> it is desirable that on any Athena workstation or dialup, one can
> build Athena packages. Basically, I'm wondering whether dropping
> apt-file might be a better solution.
>
> -Tim Abbott
>
>