Bug 64511 - alternatives assumes incorrectly, gives bad directions
Summary: alternatives assumes incorrectly, gives bad directions
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: chkconfig
Version: beta3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-06 22:59 UTC by Joshua Jensen
Modified: 2014-03-17 02:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-01-31 21:11:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Joshua Jensen 2002-05-06 22:59:26 UTC
Description of Problem:

The alternatives command, when it says "Enter to keep the default[*]", assumes
that we haven't already choosen something else.  If I configure postfix as the
mta to use, sendmail still has a "*" by it (indicating that it is the system
default), but "Enter to keep the default[*]" isn't true.... it doesn't keep (or
set) the sendmail[*] default.  It shouldn't... it is supposed to keep _MY_
default[+] (which is postfix).  So the bug isn't alternatives behavior, just the
wording of what exactly pressing enter will do.

Expected Results:

Perhaps it should say:

"Press enter to keep the current choice[+], or type selection number:"


Thanks.

Comment 1 Joshua Jensen 2002-06-05 15:06:30 UTC
This bug could perhaps be fixed before translations for the next release become
an issue.  Marking this bug as Beta Program only.

Comment 2 Joshua Jensen 2002-10-01 21:03:41 UTC
Same old bug... and so easy to fix too!

Comment 3 Joshua Jensen 2003-01-03 17:44:50 UTC
This can't be that big of a change:

Press enter to keep the current choice[+], or type selection number:




Has the string freeze happened yet?

Comment 4 Bill Nottingham 2003-01-31 21:11:49 UTC
Fixed in 1.3.7-1.

Comment 5 Bill Nottingham 2003-01-31 21:12:21 UTC
make that 1.3.8-1

Comment 6 Joshua Jensen 2003-01-31 22:21:49 UTC
Thank you!


Note You need to log in before you can comment on or make changes to this bug.