I really liked that you could install on btrfs subvolumes and edit any relevant configuration files. It also gave me a better idea of what is needed for Linux installation.
It seems both arch anywhere and architect have many features I would like to have in manjaro installer. Neither seems sufficiently complete or polished enough for official cli-installer. They would need more serious reworking than I initially thought. Maybe some parts of the original cli-installer...
It seems that architect does multiple pacstrap operations, while arch anywhere collects package list and installs them with one pacstrap. Latter option seems better. Would also be easier to modify for manjaro use.
If I try to build cli-installer, I would maybe start with arch anywhere as base and add parts from other installers. On the other hand, I prefer the overview approach of the old manjaro installer. Arch anywhere just goes forward step by step.
Because there are so many good parts available, it would probably not take too much skill to make a new installer. However, it would be so big project that I probably don't have time for it.
Now Calamares installs by default into @ and @home subvolumes if you select btrfs. If other subvolumes are on the partition, they should not be overwritten if they are not named @ and/or @home, but I need to check this. For more editing and customizing you will need to mount the installed system before the first start.
I've just tested it, it gives the following error and the installation is stopped
Boost.Python error in job "mount".
Command '['btrfs', 'subvolume', 'create', '/tmp/calamares-root-l7rcqgxw/@']' returned non-zero exit status 1
File "/usr/lib/calamares/modules/mount/main.py", line 124, in run
File "/usr/lib/calamares/modules/mount/main.py", line 74, in mount_partitions
root_mount_point + '/@'])
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
To add: I created a snapshot @ -> @kde and @home -> @kdehome, deleted subvolumes @ and @home (first @/var/lib/machines ), then Calamares was able to install to the same partititon.
The only think I don't like about Calamares is that I can't chose were I want to boot loader to be at. Even when I build the partition on another different HD. It just think I don't know what I'm doing and auto pick /dev/sda no mater what.
I dunno, for me networkd works better. Netctl always felt somehow unreliable and complicated. And it needs root password to connect to a WiFi! Although networkmanager is quite ram hungry, the ease of use of nmtui kinda makes it worth it.