OK, I'm trying to convert that rpm -- it's not easy to chase the missing library one by one, installing and creating symbolic links to wrong versions of a library, and now I hit an especially troubling:
MegaFuse: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by MegaFuse)
Firstly I don't understand what this message wants me to do. Then, I have a doubt I'm approaching this a correct way: maybe it's better to go and try to build the source myself, or will it be even longer?
I made these 3 modules to see if it works for you too.
1) Download the three modules, Put them in a folder - I named it MegaFuse - in "modules" or in "optional".
2) Extract the module "MegaFuse-x86_64-1wre", and in the folder /usr/bin, open the megafuse.conf file and edit your user name and your password for your cloud storage by "mega.nz". Build the module again. I mount it in /mnt/mega and for that I created the mount point in the module. When you activate the module, the mount point will be created.
3) Activate the modules typing "activate MegaFuse/"
4) Connected to IN, open a console and type "MegaFuse" (without the " "!) .
If you were lucky, you are connected to your cloud storage!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!
2. Other steps you suggested are not really needed. Instead, once activated, copy the megafuse.conf file into your home directory and edit by entering your account name and mount point, but NOT the password. That way the MegaFuse will prompt to type the password each time, which is safer.
I still can't find where it keeps the cache?! As I seem to have to keep an eye on it myself to see if it grows too large? The cache is by the way the key advantage as compared to the megasync client where you have to keep the complete copy locally.