You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On NixOS, OneClick installs do not work, because MimeType handlers are not allowed from ~/.local/share/applications, which is the LocalApplicationData directory there. In order for the scheme handlers to be registered, they have to be put into a particular place when the package is being built, and runtime modifications to the desktop files are not possible afaik. This restriction is beneficial to NixOS users, as it makes the behavior of their OS more predictable & reproducible.
I've been able to fix OneClick installs in NixOS/nixpkgs#345883 by recreating the desktop files normally created at runtime. However, this introduces a chance that the desktop files there will become out of sync if you make any changes to them here or add new protocols. Plus, it seems like if I toggle the options to enable OneClick installs in the app, the generated desktop file actually re-breaks OneClick installs.
Would it be possible to include static versions of these desktop files for linux, and stop generating them at runtime? This would give packagers the ability to handle the files differently between different linux distributions, and would reduce size and complexity of the binary itself.
As for the options to enable the oneclick installs, they could either:
be removed, since modern browsers generally require users to opt-in to allowing a site to open links with an x-scheme-handler anyways, or
change the way the --install flag is handled, aborting the OneClick install immediately if disabled.
Big thanks for writing a mod manager that works on Linux ❤️
The text was updated successfully, but these errors were encountered:
On NixOS, OneClick installs do not work, because MimeType handlers are not allowed from
~/.local/share/applications
, which is theLocalApplicationData
directory there. In order for the scheme handlers to be registered, they have to be put into a particular place when the package is being built, and runtime modifications to the desktop files are not possible afaik. This restriction is beneficial to NixOS users, as it makes the behavior of their OS more predictable & reproducible.I've been able to fix OneClick installs in NixOS/nixpkgs#345883 by recreating the desktop files normally created at runtime. However, this introduces a chance that the desktop files there will become out of sync if you make any changes to them here or add new protocols. Plus, it seems like if I toggle the options to enable OneClick installs in the app, the generated desktop file actually re-breaks OneClick installs.
Would it be possible to include static versions of these desktop files for linux, and stop generating them at runtime? This would give packagers the ability to handle the files differently between different linux distributions, and would reduce size and complexity of the binary itself.
As for the options to enable the oneclick installs, they could either:
--install
flag is handled, aborting the OneClick install immediately if disabled.Big thanks for writing a mod manager that works on Linux ❤️
The text was updated successfully, but these errors were encountered: