[2525] in Kerberos-V5-bugs
krb5-admin/245: fail gracefully if tcl is not available
daemon@ATHENA.MIT.EDU (bjaspan@MIT.EDU)
Tue Nov 26 15:31:33 1996
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: bjaspan@MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, bjaspan@MIT.EDU
Date: Tue, 26 Nov 1996 20:30:26 GMT
From: bjaspan@MIT.EDU
Reply-To: bjaspan@MIT.EDU
To: krb5-bugs@MIT.EDU
>Number: 245
>Category: krb5-admin
>Synopsis: fail gracefully if tcl is not available
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: bjaspan
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Tue Nov 26 15:31:01 EST 1996
>Last-Modified:
>Originator: Barry Jaspan
>Organization:
mit
>Release: 1.0-development
>Environment:
System: IRIX the-tick 5.3 02091401 IP22 mips
>Description:
IMO, this is not a priority for 1.0.
If tcl is not available at configure time, the build system does
mostly the right thing: it does not build kadmin/testing/util/*tcl,
and it does not run the kadm5 unit tests. However, it's warning
message in kadmin/testing/util is a single line, easily missed; it
should be a "+++"-style error like the unit-test directories.
If a site acquires tcl after configuring, re-configs the unit-test
directories, and runs gmake check, start_servers will fail because it
cannot find kadmin/testing/util/*tcl, which were not built because tcl
was unavailable. start_server should check for the existence of these
programs explicitly a print a useful error message (like, "now that
you have tcl, cd into kadmin/testing and run configure and make").
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted:
