Fleck does not require a compiled executable to be installed.
As long as you have bash Fleck will work. For scsh you have to have to install platform specific executable. If it is available in a particular distro, perhaps it is not that bad.
I write, these days, a lot of Ansible installation tools For Multiple versions of (and almost bare) linux, freebsd, openbsd (and hopefully at some point for DragonFlyBSD).
Today, I have to write shell-specific scripts to do application-centric process management, application-centric backup preparation steps, health monitors, smoke tests and so on.
To minimize my work, I instruct Ansible to preinstall bash everywhere... and then I run the bash scripts.
But writing bash scripts is, well,... unsettling (hard to get used to primitive return values, lack of normal enumerated parameter passing and so on)
With Fleck (at least this is my reading), I will be able to install Fleck via Ansible and then write all the scripts in Scheme (which I much prefer compared to bash, zsh or anything else).
I guess, if, in the future, Fleck will help me to avoid worrying about Powershell, kornshell and so on -- I would be delighted.
Sort of like shell-vm on top of base shells :-)
>hopefully at some point for DragonFlyBSD
What advantage of DragonFlyBSD you see today over other OSs?
Our needs are such, that writes are relatively rare, and go into one cluster, while reads of our blobs, need to go to geographically distributed nodes, whose disk topology is different (less capable) than that of a muster, plus they have somewhat-unreliable connectivity to the master.
So Hammer's network-problems-tolerant streaming replication and offline de-duplication is attractive, at least conceptually.
Wait a minute. I may be mistaken, but I thought Ansible needed Python on the managed machines, to run some of the modules. Afaik it uploads some Python code via ssh before doing the work proper.
(https://docs.ansible.com/ansible/latest/installation_guide/i...)