The author updated the installation process for Direct Commander on Linux, finding that the Bottles software and Flatpak are unnecessary. The application runs on a standard Wine installation from the WineHQ repository, which avoids issues with game-oriented builds like Proton or Soda that fail due to incomplete DirectComposition support.
The installation process involves using a standard Wine prefix and manually extracting the application from the installer's NSIS archive. This method provides better system font integration and improved performance compared to the previous sandbox-based approach. The author also noted that the official auto-updater fails silently because it attempts to trigger a non-interactive installation process that hangs.
To handle updates, users can manually run the installer executable found in the application's pending folder. The author also highlighted the importance of path validation in scripts, noting that a flawed deletion script accidentally removed a working installation because it failed to correctly distinguish between similar directory paths during a check.
The updated configuration is now the recommended path for new users, while existing setups using Bottles remain functional. The author emphasizes that the initial working configuration is rarely the most efficient and that thorough testing of safety scripts is essential to prevent unintended data loss.
