Architecture compatibility?

[Slackadays]

I noticed in the readme that Clifm works on x86 and ARM. Is this just the architectures it's been tested with, or does it really only support those two? If it only supports those two, then that's a problem.

[leo-arch]

Hi @Slackadays. No tests have been made beyond X86 and ARM, though it will most likely work on other architectures (as far as I know, there's nothing architecture-specific in clifm's code).

[Slackadays]

You could add a bunch of build and test GH actions to verify that clifm works everywhere, kind of like Clipboard does. I noticed that the only real action right now verifies building on one platform. Does that sound like a reasonable proposition?

[leo-arch]

Absolutely! I've seen what you've done with Clipboard's builds, and it's pretty cool.

[leo-arch]

Hi @Slackadays! Forgot to say that we've been successfully building distro-specific packages for over a year (using the OpenSUSE Build System) for these architectures: x86_64, i585, armv7l, aarch64, and ppc64le.

[leo-arch]

Thanks Slack! Nice find, elegant solution.

[Slackadays]

Glad to help as always! 🙏

[leo-arch]

I got a first implementation working (78ceac0). The lag should be mostly gone now.

[leo-arch]

Hi @Slackadays. Have you tried this fix?

[Slackadays]

Hey @leo-arch! I just tried the latest commit on the LicheePi (using Ubuntu now due to built-in ethernet drivers) and it's a whole lot faster after doing each command. This new write time check seems to work really well :)