The current version of emerge does print " "+yellow("*")+" Type "+green("emerge --help config")+" to learn how to update config files." in the end of successful emerge, but running `emerge --help config` in portage 2.1 tells "*** Deprecated use of action 'config', use '--config' instead". I assume the former needs to be updated.
Well, the --config option is actually something competely different from what is described by `emerge --help config`. Perhaps we should drop the `emerge --help config` feature and simply document it in the portage.5 man page.
*** Bug 137592 has been marked as a duplicate of this bug. ***
Today I also noticed the warning: # emerge --help config *** Deprecated use of action 'config', use '--config' instead Config file management support (preliminary) ... To my surprise the below command also worked, but without a warning: # emerge --help --config Config file management support (preliminary) ... Overall this surprised me a bit, so I began to dig deeper. Obviously, 'emerge --help config' and 'emerge --help --config' mean that "config" or "--config" is a parameter to the "--help" option. Even Subversion has the notion of documenting its commands in a similar way, although it's "svn help <command>". Recent changes in portage (emerge?) wrt. prefixing parameters with double dashes, like 'emerge --sync' in favor of 'emerge sync' do seem reasonable. But 'emerge --help --config' or 'emerge --help --sync' (without warnings) in favor of well documented, old-style (but with warnings) 'emerge --help config' or 'emerge --help sync' may confuse (a bit) some users. OTOH the new syntax is consistent with the new style actions, so I appreciate that. Currently it's "emerge --sync" and "emerge --config <package>", so asking for help regarding these example actions with "emerge --help --<action>" also seem reasonable. (And in reply to comment #1) > Perhaps we should drop the `emerge --help config` feature > and simply document it in the portage.5 man page. This would break the "compatibility" with existing docs on the net. I've found several of them claiming that 'emerge --help config' is the way to get more help on the CONFIG_PROTECT feature. That's how I stumbled upon this warning in the first place. IMHO the warning should be kept and logic for processing emerge's parameters could be enhanced, instead of silently dropping features. Text of the warning could also be changed, stating verbosely that "emerge --help config" is incorrect and "emerge --help --config" should be used. Currently the warning is consistent with the "emerge config <sth>", but not with the "emerge --help config". How about this one? *** Deprecated use of action '--help config', use '--help --config' instead And if the relevant information is ever going to be moved to the man page (which is completely valid from my POV), the old behaviour still could work but the text displayed should point users to the correct man page.
Created attachment 91266 [details, diff] changes "--help config" to "help --protect", also in the docs > Text of the warning could also be changed, stating verbosely that "emerge > --help config" is incorrect and "emerge --help --config" should be used. As comment #1 says: "--config" has nothing to do with "--help config". The patch proposes to change the latter to "--help protect".
*** This bug has been marked as a duplicate of bug 137483 ***
