|Mirko Brombin f730b32546||12 hours ago|
|build-aux/meson||2 weeks ago|
|data||1 day ago|
|po||1 week ago|
|src||13 hours ago|
|CONTRIBUTING.md||1 month ago|
|COPYING||2 weeks ago|
|LICENSE||1 year ago|
|README.md||3 days ago|
|ld.so.conf||2 days ago|
|meson.build||2 weeks ago|
|pm.mirko.bottles.json||12 hours ago|
|screenshot-0.png||3 days ago|
|screenshot-1-1.png||3 days ago|
|screenshot-1.png||3 days ago|
|screenshot-2.png||3 days ago|
|screenshot-3-1.png||2 days ago|
|screenshot-3-2.png||2 days ago|
|screenshot-3.png||2 days ago|
|screenshot-4.png||1 week ago|
|screenshot-5.png||1 week ago|
|screenshot-6.png||2 days ago|
|screenshot-7.png||1 week ago|
|screenshot-8.png||1 week ago|
|screenshot-9.png||3 days ago|
|screenshot-10.png||3 days ago|
Easily manage wineprefix using environments⚠️ This version is under development.
Disclaimer: This is a development version (alpha), you will find bugs, black holes and monsters under the bed. Be careful.
git clone https://github.com/brombinmirko/bottles cd bottles git checkout develop flatpak-builder --user --install build-dir pm.mirko.bottles.json flatpak run pm.mirko.bottles
Bottles was born in 2017 as a personal need. I needed a practical way to manage my wineprefixes. I hate the idea of using applications that install me a version of wine for each application and I decided to create this application, based on the concept of using one or more wine prefixes as a "container" for all my applications.
In 2020 thanks to Valve, we have access to Proton. An optimized version of Wine for gaming. Thanks also to other projects like DXVK/VKD3D/Esync/Fsync/Shader compiler and others, we can run a large set of video games designed for Windows, on Linux.
The idea of creating an environment-based wineprefix manager comes from the standardization of dependencies and parameters necessary to run a game. On the other hand, we have software (often not up to date) that require environments and configurations different from those used in gaming. Hence the idea of managing separate environments.
Because they are similar but different applications. I want to create environments that contain more applications and games and where the wine version can be updated.
I also want to be able to export my bottles allowing easy sharing, with or without applications. In POL/Lutris we have the concept of "with this version of wine and these changes it works". In Bottles the concept is "this is my wine bottle, I want to install this software".
The goal with this version is also to integrate with the system in the best possible way. Being able to decide in a few bottles to run an .exe/.msi file and have control over it without having to open Bottles for each operation.
Bottles is close to what wineprefix means, since v.2 it provides a simplified method to generate environment-based bottles and thanks to other tools it simplifies the management but nothing more.
Idk. Really. Keep an eye on the develop branch, sooner or later there will be an almost stable release
Maybe in the future, not now. I will keep both branches updated for a long time.
Probably yes. I would like to allow the conversion of the old wine prefixes in v.2.
Unlike the previous versions, now the bottles are saved with JSON sheets containing all the instructions and settings, such as the version of wine/proton in use, the various active flags etc.