a5ae411c55
consider the following scenario, admittedly one that is not possible today: * There is an "install model" that is required for server and not desktop (let's say "mirror") * The user initially selects a desktop install and moves through the screens until they are asked for confirmation. * At this point the user moves back through the screens and selects a server variant. Now the application state of NEEDS_CONFIRMATION is misleading; the state needs to move back to WAITING until the mirror model is configured. This is all probably excessively general but I feel like the core control flow of the installer needs to be able to handle this sort of thing... |
||
|---|---|---|
| .. | ||
| tests | ||
| __init__.py | ||
| filesystem.py | ||
| identity.py | ||
| kernel.py | ||
| keyboard.py | ||
| locale.py | ||
| mirror.py | ||
| network.py | ||
| proxy.py | ||
| snaplist.py | ||
| ssh.py | ||
| subiquity.py | ||
| timezone.py | ||
| updates.py | ||