Changes to Navigation? about raspi-config HOT 5 CLOSED

The script will be maintained in future, and it does have a full set of command-line options - far more, in fact, than it had before the GUI was introduced, as the GUI uses said command-line options for all functionality.

from raspi-config.

I can't believe that the use case for automation (via cli) is not seriously going to be supported. I know of several environments that have many Pi devices, and drive the configuration via ansible, but ansible can't do everything with ease, where an answer file, or robust cli is the true need. Please, seriously reconsider continuation of the cli aspect. Sorry, but the GUI only model, is just plain wrong for serious use of Pi devices. Are you not trying to encourage Pi devices at part of IoT? There is just one valid use case for robust cli.

from raspi-config.

Going forward, the recommended use of raspi-config is via the rc_gui desktop GUI rather than the command-line raspi-config itself. raspi-config will be kept functionally up to date for people who don't want to use the GUI, but we're unlikely to do much in the way of usability improvements to it from now on.

from raspi-config.

There is a use case for maintaining full functionality of the script with a full set of command line options. This will makes sense for people who need to automate the setup of Raspbian for educational or development purposes.

from raspi-config.

Please read what I wrote above.

We are not going to stop supporting configuration via the CLI; in fact, the GUI application relies on the CLI configuration tool as a backend. The CLI configuration tool remains under continual development, as the number of ongoing check-ins to this project demonstrates.

What we are not doing is making usability changes to the CLI tool, as the GUI tool is where usability improvements are made. Functionality changes will continue to be made to the CLI tool as needed.

from raspi-config.