[Slackbuilds-users] All-writable directory under /opt

[Daniel Prosser]

Thanks for the ideas. I like the idea of using the setgid bit, but I'm 
having trouble getting it to work. First, the main executable is a 
wrapper script, which may be a problem, but even applying the setguid 
bit to the binary file and foregoing the wrapper script (doing the stuff 
the wrapper script would have done manually in the shell for testing 
purposes) results in library import errors. I assume this is due to 
permissions somehow, but I don't really understand why.

After some more testing, I don't think that having the SlackBuild script 
copy or symlink one of the stockfish executables will solve the problem. 
There is apparently also a setting in the user config directory that it 
looks for, and if that isn't present, it will try to go through the 
copying process anyway.

Asking the user to run as root the first time would work, but I would 
also have to tell them to then copy the configuration directory from 
/root to their user directory and set permissions accordingly, which 
seems rather unwieldy and inconvenient. In a related idea, what about 
installing the program with some group ownership (say "LucasChess") and 
asking the user to join that group before running?

Dan

On 5/4/24 00:55, B. Watson wrote:
>
>
> On Fri, 3 May 2024, Daniel Prosser wrote:
>
>> The copy it makes is called stockfish-16.1-64. On my machine, it 
>> seems to have copied the bmi2 version, but maybe the plain -x86-64 
>> version would be more universal. (For that matter, if I take this 
>> approach, I'll probably just make a symbolic link instead of wasting 
>> disk space with a copy.)
>
> I can think of one more approach... assuming the stockfish-16.1-x86-64
> binary will run on anything x86_64 (because it doesn't have
> fancy CPU-specific optimizations), pre-create the symlink to that
> one. Advise the user that the other engines exist (in the README)
> and give a short set of instructions on how to choose the right one
> (basically as simple as, rm the symlink, run the engine as root once).
>
> This way, people who just install it without paying much attention
> will at least get a working (if unoptimized) package.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>