Conversation
|
I've been thinking about this thumbnailer stuff and I don't think we want it by default for builds - only for "make install" and then preferably as an option. I still think it's more of a packaging thing. I just don't like the idea of saving a file from email or off the internet and having software open it by default. @ruevs what do you think? |
|
This is quite far from my daily computer use since I do not use (desktop) Linux regularly. But it definitely sounds like a distro/packaging problem. Whether the default |
|
This PR aligns the .thumbnailer with the .desktop file.
Is SS so insecure? I am confused by this. So don't use thumbnails then. Every thumbnail operates the same way. I'm so confused I don't even know where to start.
The alternative being... software compiled by others and installed with root privileges... ? |
What I meant is that when I compile something I simply run it from the location where the compilation process "dumped" the executable. This is perhaps a bit nerdy, but if I've gone to the trouble of compiling the source it means I'm either tracking the bleeding edge of something, or working on it. So "installing" is just an extra step I skip. This is especially true for SolveSpace, which will happily run from anywhere... on Windows is does not even have an installer - it is a single .exe with no dependencies. |
This edit aligns the thumbnailer feature with PR #1673. Specifically, it modifies the solvespace.thumbnail file to point to the installed executable. This means that if a user installs solvespace to ~/.local, the thumbnailer will work for that user.
This is necessary because ~/.local/bin is not normally included in the default PATH environment variable.