Newby :) - Can I install the "Worker" binary from the dev's web site?

[nitram]

Just retested, worker is saving configuration changes upon re-open and reboot.

Not sure what 'save worker state' is about, doesn't remember last opened directories on re-start, should it?

worker configuration -> import/export: did you try importing via this method rather than just a copy/paste of old config?

[handy]

My Worker doesn't behave quite the same as yours. Reboot doesn't help it.
I removed the config from my other machine.
Yes, the versions are different, I'm running 3.8.0 64bit (though I doubt that, that matters, for the config files at least).

Perhaps save worker state saves the size/position of it from when you close it, for next time? I don't know, I always run it full screen & auto load it via Openbox ~/.config/openbox/autostart file.

Worker opens each of its file lister windows in the directories that you are set via the List view configuration -> Initial directories sub-section, found in the left hand column of the config GUI.

No, I didn't import the config file using that available option (never do when I set up a new system, I just dump the whole directory ~/.worker over the top of Workers initial useless stuff. So I should try that, you never know your luck.

[nitram]

Hi handy.

Recompiled avfs with recommended fuse and liblzma support, plus proper TC compile configuration (maybe my mistake). Works okay. Manually built new 64-bit worker.tcz, based on worker_3.8.0-1_amd64.deb, the same link pointed to from the worker site. Me thinks same version you're using. I don't have a 64-bit system to test, hopefully okay.

The worker.tcz.dep file was updated to reflect fuse and liblzma. If you don't have these extensions in /optional use Apps to download them before loading new worker.tcz. Recommend removing old configs before attempting to load new extension and reboot beforehand if old worker is loaded into RAM.

Will PM new download links and provide avfs compile notes should you want to compile on your 64-bit system (not sure if this would make a difference?).

[Misalf]

Maybe it's better to go back some versions where it compiles using GCC 4.9.1?

[nitram]

Hi Misalf. Will wait until  handy  tests updates/provides feedback. Since i only have 32-bit system, should this then preferably be compiled by a 64-bit system? My understanding is 64-bit systems run 32-bit software, but would 64-bit software be more compatible/better? Although the release date for TC 7 is unknown, query whether it will have an adequately updated GCC?

[Juanito]

If you only have a 32-bit system then you need to compile a 32-bit worker extension. The 64-bit version of tinycore will not run 32-bit apps.

The 7.x version of tinycore will probably use gcc-5.2.0, but it will be a while before it is available, so I'd recommend you choose a slightly older version of worker that will compile with gcc-4.9.1.

[handy]

Thanks to all concerned for your extremely helpful input.

I'm not sure whether I'm going to get to testing today or not, some unexpected things have come up. If not today then tomorrow.

I've a 64bit CPU, but I installed 32bit TC. My Manjaro install is 64bit, so I probably can't bring the Worker binary over from there, though the ~/.worker/conf file should be fine, as it is basically just text.

If an older version of Worker is used, I'm pretty sure that it won't accept the v3.8.0 ~/.worker/conf file. If that is how it has to be done with TC (currently at least), then that is OK. I will duplicate the settings that I want/need, to use in whatever version of Worker that I need to run on TC.

Thanks once again for all the help & sorry for moving a bit slow here & there.

[nitram]

If you installed 32-bit TC then my understanding is the 32-bit worker.tcz originally provided should work fine. Just use the most recent avfs.tcz PMed yesterday, which was compiled proper and includes fuse support and the updated .dep file. All should be good. Looking forward to your feedback. My impression is that worker itself is functioning okay, it's just an issue with setting up your configuration. Maybe i'm mistaken.

Went to the worker site and tried compiling older versions, including 3.8.0, 3.7.1, 3.7.0 and 3.6.2, all with the same compile error.

Reviewed the compile error again, same as quoted by Misalf in post #2. The error message actually appears to suggest using GCC 4.8, TC uses 4.9, so doubtful that waiting for the TC 7 release will be helpful.

Anyway hope the 32-bit worker.tcz and 32-bit proper compiled afvs.tcz works for you handy.

[curaga]

Compile latest Worker on TC5? I doubt it uses image libs.

[nitram]

handy has left the building   Query: worker.tcz was built from precompiled .deb, as it would not compile in TC 6. It's primary dependency, avfs.tcz was formally compiled. The extensions appear to work well for an alternative file manager. Can they be submitted, marked in the info file as 'testing' or 'created from precompiled .deb' or similar? My hunch is no, just want confirmation. If acceptable then may submit, otherwise delete. Thanks.

[curaga]

Please don't submit extensions made from precompiled binaries.