wine-staging VS HomeBrew

Now you can't just go from vanilla WINE to WINE Staging by installing stuff. You would have to patch the source code of WINE with all those patches: https://github.com/wine-staging/wine-staging/tree/master/patches and then compile it yourself.

Read this for more info: https://wiki.winehq.org/Wine-Staging

I've got the source from here and applied the patch as it says here

vkd3d-proton: - occasional upstream pending patches wine: - uses proton's bleeding edge wine base: https://github.com/ValveSoftware/wine/tree/experimental-wine-bleeding-edge-7.0-20190-20220716-pe79367-w7a9d8c-d5aa943-v5b7313 - adds wine-staging on top of it: https://github.com/wine-staging/wine-staging/tree/master/patches - adds FSR patches on top of it: https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/proton/48-proton-fshack\_amd\_fsr.patch - adds a handful of other game fixes on top of it: https://github.com/GloriousEggroll/proton-ge-custom/blob/e01207aafe539d8d3ed49301665da717340e4c1d/patches/protonprep-valve-staging.sh#L295 - removes the proton-specific steamclient changes so that it works as a normal wine build: https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/proton/0001-De-steamify-proton-s-WINE-so-it-can-be-used-as-a-sta.patch ffmpeg: - we enable some codecs not available in steam's ffmpeg gstreamer: - we enable some codecs not available in steam's gstreamer protonfixes: - these are python scripts that automate installing various winetricks and/or other per-game tweaks. this achieves the same thing most lutris installers perform. -------------------------

USE "HOMEBREW" https://brew.sh/ Or "MACPORTS" https://www.macports.org/ As subsystem or wrapper to help wine to be stable. I trying homebrew for a week right now with many versions of wine ( stable & bev , etc The fastest WINE wrapper updated is WINE STAGING. 🍷 https://github.com/wine-staging/wine-staging

Install Wine Staging and winetricks. Then create a new 64 bit prefix. You can run winetricks for this.

It's possible there's blockers for it not being updated, but you can also get a general idea as to how long updates on Fedora's end takes by comparing the dates on that site to the releases on Staging's GitHub.

These patches are missing: https://github.com/wine-staging/wine-staging/tree/master/patches/winepulse-PulseAudio_Support

FFXI should run fine on Steam Deck as it's reported as Gold in ProtonDB but, as I'm used to play the game on Windows, it can be fully enhanced/HD remastered with a lot of graphical and QOL community mods (Ref. here) which are all based on Windower - This is probably a core issue for the SD trying to run this third party/"dll injector". After having a chat with Windower support on Discord, I found out that the main issue is this commit in Wine. Now it would be great to know if this commit will be included in the Proton build used by the SD - Keeping it short: Proton is basically Valve's implementation of Wine. I'm definitely going to try this as soon as I have my hands on the SD as FFXI is still such a great/unique MMORPG and I would also suggest to check it out to everyone having a few friends to bring in.

Source: git mirror's contributor graphs located at wine-staging.

Homebrew is a highly popular package manager on macOS and Linux systems, enabling users to easily install, update, and uninstall command-line tools and applications. Its design philosophy focuses on simplifying the software installation process on macOS, eliminating the need for manual downloads and compilations of software packages.

Homebrew - package manager for linux-based OSs.

Package Manager: Homebrew

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

Are you using SQLite that ships with macOS, or SQLite installed from homebrew?

I had a different problem in the past with the SQLite that ships with macOS, and have been using SQLite from homebrew since.

So if it’s the one that comes with macOS that gives you this problem that you are having, try using SQLite from homebrew instead.

https://brew.sh/

Before we begin, make sure you have Homebrew installed on your Mac. Homebrew is a package manager that makes it easy to install software and dependencies. You can install Homebrew by following the instructions on their website: https://brew.sh/

I’m on MacOS and erlang.org, elixir-lang.org, and postgresql.org all suggest installation via Homebrew, which is a very popular package manager for MacOS.

I have always either installed Node from the installer provided by the Nodejs website or, via Brew in macOS. I have also used nvm in the past but did not know that there was a best practice to guide us.

A running Rails application needs a database to connect to. You may already have your database of choice installed, but if not, I recommend PostgreSQL, or Postgres for short. On a Mac, probably the easiest way to install it is with Posrgres.app. Another option, the one I prefer, is to use Homebrew. With Homebrew installed, this command will install PostgreSQL version 16 along with libpq:

On a macOS machine, you can use homebrew by running the command.