[1392] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: ADDENDUM: Re: build system redesign ideas

daemon@ATHENA.MIT.EDU (srz@MIT.EDU)
Mon Jul 15 14:38:30 1996

From: srz@MIT.EDU
Date: Mon, 15 Jul 1996 14:38:14 -0400
To: bjaspan@MIT.EDU
Cc: krbdev@MIT.EDU

I figured I would throw my $.02 in here...

   Why?  Technical reasons, or political/ideaological ones (ie: Windows
   users won't demean themselves by touching unix tools)?

Human nature.  There's a learning curve associated with foreign tools,
with all the nuances of command-line options, directory structures,
etc.  Unix-based tools are not likely to deal with DOS brain-damage
like 8.3 file names, 640k memory limitations, etc.  Mac and Windows
programmers are used to project-based systems like Code Warrior and
Visual Basic.

Some of these are technical issues.  DI is a mixed system shop where
everyone is a Unix weenie, and I wouldn't *dream* of using gmake as
the make engine.  It has the potential of causing too many headaches,
and I can't see the effort justified in terms of savings.

The question here comes down to optimization.  Are you optimizing for
kerberos5 development effort, or are you optimizing for kerberos5 user
effort?

	-stan

home help back first fref pref prev next nref lref last post