Add Bottles Support

[thw26]

https://usebottles.com/

[ctrlaltf24]

If we wanted to do this, we could probably be added as "Software" in their app catalog https://github.com/bottlesdevs/programs/tree/main/Software

[thw26]

Also worth exploring. We had one user who was pretty gung-ho about Bottles but I think it became harder to maintain following ICU support.

[mattvisa]

Has there have been any progress on this feature request? I would like to add my support for it. Thank you for all the work you're doing on this.

[ctrlaltf24]

Nope no progress, nor any plans to. What we do is very similar to bottle's general idea: put one wine application in its own "bottle" with the ideal version of wine and dependencies and whatnot. Therefore from a functionality point of view we're already advantage of some of the advantages of why you'd want to use bottles.

I'm not sure the process to build a bottle, but ideally it would be a CLI command on the normal Oudedetai binary to make a bottle (this way we could actually maintain it). Then if it'd help the bottles community we could export that artifact (again knowing nothing about bottles) to a cache so normal bottle users wouldn't need the oudedetai binary

If you wanted to work on this, I'd recommend:

• reading bottles documentation for making a new bottle (for distribution)
• running the oudedetai binary and taking a look in ~/.local/share/Faithlife-Community for what we already do
• then looking over the python (specially in installer.py)
• then start scripting out a way to export what oudedetai already does to a format bottles can import. Alternatively if that isn't practical we may need to have the installer run inside the bottle somehow (MUCH more complicated, try the other approach first. I know this one sounds simpler but it's unlikely to be simpler). Feel free to make a new bottles.py if you want to organize your code that way

Feel free to reach out to us here or on telegram if you need support developing this.

Make sure the work you do is:

• a result of the oudedetai binary's execution (this is CRUCIAL for supporting this wine bottle in the future) (I'd almost way this is not negotiable)
• execution of bottle or normal oudedetai as similar as possible (same wine version, wine binaries, etc) (again making support and maintenance possible)
• readable/easy to follow. In order to maintain this going forward it needs to be clear what does what.