Add CLI tool for system configuration

[codefiles]

Add a CLI tool called archconf to help configure the system during a manual installation.

$ archconf --help
usage: archconf [options] root

Options:
 -t, --timezone <Area/Location>    Set system timezone (e.g., Europe/Berlin)
 -g, --gen-adjtime                 Generate /etc/adjtime for hardware clock
 -l, --locale <locale>             Set system locale (e.g., en_US.UTF-8)
 -k, --keymap <keymap>             Set console keymap (e.g., de-latin1)
 -n, --hostname <name>             Set system hostname
 -h, --help                        Display this help message
 -V, --version                     Display version

Example usage:

# archconf \
> --timezone Area/Location \
> --gen-adjtime \
> --locale en_US.UTF-8 \
> --keymap de-latin1 \
> --hostname yourhostname \
> /mnt

Would anyone want something like this?

[svartkanin]

Sounds very intriguing, would this be solely to generate the configuration and then use it with archinstall?
What would be the use case for it in combination with archinstall and what would the output of the above command look like?

[codefiles]

I was thinking a separate tool from the archinstall TUI that uses parts of the code for the configure the system steps of a manual install.

More like a convenience script like genfstab is for /etc/fstab.

There would be no output for a successful run. A user would perform a pacstrap then the command I demonstrated above (using the options they require) for example. See the example code here: #4149 (comment)

I figured since archinstall is on the ISO, some users may not want to navigate a TUI and may find this as a useful alternative. I like the TUI but thought this would add another option. Maybe the idea is lame.

[svartkanin]

So the intention here would be to have the user partition, format, pacstrap and then run the configuration script?

I think it would still make sense then to have it compatible with the archinstall configuration file. I'm thinking of the case where a user would go through the TUI, save their configuration then install which may break at the format/partitioning level, then they could do that step manually and run the config? It sounds similar to the pre-mount option that will then install the system, except that the pacstrap should also be done by the user and then apply the config?

Looking at the current guided.py anything after the minimal_installation would be part of the configuration? Sounds like this could be extracted from guided into its own module and then use it in guided and the config :)

[refcar]

The idea is interesting, but it's not clear what will happen with the disk partitioning?:)

[codefiles]

Here is another use case. Let's say a user wants to create an Arch Linux container in an Arch Linux host.

# pacstrap -K -c ~/MyContainer base
# archconf -l en_US.UTF-8 -n archlinux ~/MyContainer

https://wiki.archlinux.org/title/Systemd-nspawn#Create_and_boot_a_minimal_Arch_Linux_container

But systemd commands work in the container so this is useless I guess. This does the same thing inside the booted container:

# localectl set-locale en_US.UTF-8
# hostnamectl hostname archlinux

[svartkanin]

I think it would be great addition overall!