Partitions should have more flexible file system options about archinstall

[Torxed]

The following PR's is contributing towards this goal:

• #89
• #90

[Torxed]

As of 530edb5, the guided installer can detect and report the current partitioning scheme as well as the mountpoints and the filesystems in use. It does not yet have the capability to seamlessly erase the partitions according to the current setup, as use_entire_disk will erase with some pre-chosen formats anyway.

That's the next step in fixing this :) Probably we'll rely on partition.filesystem instead of hardcoding in a format, which makes sense.

[Torxed]

Moving closer to having this resolved. e2cd617 introduces a new workflow for dealing with partitions. Partitions now have a formatting lock on them through self.allow_formatting = False (default). This prevents accidental formatting of partitions.
The changes introduced also allows for the partitioning logic further ahead which is the next change to come.

The installer will check for any partitions with a target_mountpoint (those are relative mount-points to within an installation) and perform actions on those based on the information:

• partition fstype
• relative mountpoint
• encryption state

I will try to have that logic done in the next day or so.
After which users should be able to create more complex pre-configured filesystem setups as long as we support the filesystems in questions (since we need to handle unique packages and function calls for different types of filesystems).

This adds one additional step to the installer when selecting to keep the partitions, and that is to ask which partitions to use (and modify).
I've tested on a 1TB disk with multiple OS:es on it, and the end goal is to only touch those that we select and leave the others completely untouched.

[Torxed]

Almost there! The partitioning logic can now:

• Wipe entire drive
• Keep existing partitioning scheme
  • Detect if /boot is empty or not, and wipe it if it is just to be sure or keep it as is and other OS:es should be intact

There's still the selection/logic of disk encryptions and the target filesystem-type.
In the above picture the target filesystem inside the encrypted volume should be ext4 and thus /dev/sda3 got formatted as ext4 when in fact it should be formatted with luks2 and once unlocked should be formatted with ext4.

But that's just a logic tweak, after which this should be done and dusted! : )

[Torxed]

Initial tests looks promising.
Partitioning and installation passes all the way to final boot-loader installation.

The boot-loader fails due to wrong partition format ESP by the looks of it.
But I think that has to do with how I manually did parted mklabel gpt and so on when setting up the /boot to contain a fake windows loader. To see if archinstall would break or leave it untouched.

Will run some more tests later today.

[Torxed]

As of 3f8f002, archinstall now supports a more flexible partitioning scheme.
It's still a bit in it's infancy, but it should now support existing partitioning layouts. As well as other operating systems (it won't touch them) including a shared EFI boot partition. Which means you can use partial disks for the setup now by partitioning the disk before running the setup.

It also properly detects encrypted partitions and their inner filesystem (if the old disk encryption password is the same as the new one). If not, the user will have to properly define the inner filesystem upon being asked - if the autodetect fails.. or if the user don't want to auto-detect at all.

It also has the option to wipe the entire drive, which fullfills this issue and task.
I will release a release candidate later tonight for proper testing before this gets shipped into the wild.