Provide option to setup snapper if the btrfs filesystem is chosen

[neelchakrabrty]

While it is not a must have feature,I think it'd be a nice to have snapper config working out of the box.

[Torxed]

what additional things is needed other than installing the package?

[adamthiede]

I just went through this installer, and the subvolume setup is really nice. But creating a .snapshots subvolume means that snapper is unable to do it and won't create a root config. I had to unmount /.snapshots, delete the directory, run sudo snapper -c root create-config, then mount -a to get it set up properly.

So probably the following needs to happen:

1. Don't create a .snapshots subvolume
2. Install snapper package (and maybe snap-pac too?)
3. Run snapper -c root create-config in the chroot

I am entirely unfamiliar with the codebase but could try to make a PR for this if you like.

[Torxed]

Humm, previously we had to create @.snapshots in order to be compliant with snapper. I wonder what changed?

Without knowing for sure, it sounds like an issue with snapper not detecting that @.snapshots is empty and "ready to be used"? Because we don't create any content in it.

If this is a design choice, absolutely then we can create another question in the btrfs submenu asking if snapshots is desired and set snapper up.

[chalybesmith]

I agree this would be a useful feature, since the use for btrfs subvolumes are snapshots in the first place. I personally think it would be reasonable (selectable) default option to have snapshots set up by the install-script.