`just` recipe name changes are happening?
just
TThanks!
TI saw, thank you. It's better than linking it
JHmm. So it looks like bazzite-arch , the OCI container, hasn't built for the last 5 - 6 days
Blutris is crashing A LOT
BBthe logs barely give anything
Trun
lutris -di did run that
Band thats what i gotr
B
Kmight want to post in their discord, we only install the fedora rpm
Bdo you install wine from the repos or winehq?
Ta very brief search on the flushing display issue suggests trying X11 to see if it works from there
Bi assume the former since i cant find the repos for winehq
Bwithin my system
Kwe only install wine-core from fedora's repos for dependency reasons
Kyou're expected to use protonup-qt/otherwise to install Wine-GE or another better runner
Kmost install scripts also do this
TI also have not experienced wine dependency hell in Lutris in Bazzite
Bi'm trying to test lutris in a distrobox, thats why I asked about the wine dependancies
Khm? Why? We ship it as part of the image
Bthey're probably gonna need me to test it on vanilla fedora just in case idek
Hhttps://github.com/ublue-os/config/pull/181
standardization of just recipe names.
ongoing job, might actually put it back to draft until i implement the quick toggles like @EyeCantCU suggested.
but it is something that is in the pipeline for ublue config and once that is done i will take a look at the bazzite specific recipes too
it is to address the inconsistency with recipe names
https://github.com/ublue-os/config/issues/148
the goal is that several recipes will be available under 1 name like
standardization of just recipe names.
ongoing job, might actually put it back to draft until i implement the quick toggles like @EyeCantCU suggested.
but it is something that is in the pipeline for ublue config and once that is done i will take a look at the bazzite specific recipes too
it is to address the inconsistency with recipe names
https://github.com/ublue-os/config/issues/148
the goal is that several recipes will be available under 1 name like
ujust setup-nixGitHub
This patch, when complete will be the second step in addressing #148 now that we have ugum on all images which solved the need of a standardized way to select between options.
This is something tha...
This is something tha...
GitHub
I see at least three styles of enable/disable scripts in just --list: disable-updates ⬌ enable-updates disable-broadcom-wl ⬌ use-broadcom-wl use-stock-gamepads ⬌ use-ublue-gamepads Worth standardiz...
H
Toh wow
Tyeah ill talk about this in the buzz
Halso hi, i just got home from 3 hours of overtime and no lunch break today 
Tdamn!!! what the heck
Tno lunch break!?
Hmore that i worked and forgot my lunch break
Hi have held a group room hostage since august for re-imaging, inventorying of computers and configuring of new network gear and i got a message on wednesday that i had to clear out of the room today (my workdays are tuesday and friday) so essentially i got a 1 day heads up
Hso that has essentially been my workspace for the last 3-5 months 
FWhile this wine stuff is mentioned, I would like to know if it's possible to have wine setup out-of-the-box, without complicated GUI things of prefixes & such stuff like in Bottles & Lutris.
Just run the .exe & enjoy.
Or just place Windows app folder in the desired location, make desktop shortcut & run it. ($HOME/.WindowsApps or smth)
WineZGUI is not what I want.
Just wondering if this stuff I want is possible
Just run the .exe & enjoy.
Or just place Windows app folder in the desired location, make desktop shortcut & run it. ($HOME/.WindowsApps or smth)
WineZGUI is not what I want.
Just wondering if this stuff I want is possible
Tyou can just run wine out of the box. this would be separate from the container apps you mentioned
Twhether this is optimal is a different question
Tespecially if you need certain settings or flags to have things run
FFlatpaks are much harder to set out-of-the-box unfortunately compared to system stuff, so that's why I'm thinking of this approach
C
TI was just talking in the context of Bazzite. Wine is available system-wide
Tfor flatpak wine, I pretty much never recommend using it outside of Steam, Lutris, Heroic or Bottles
GAwesome news for ray tracing on AMD https://www.phoronix.com/news/RADV-RT-Much-Faster-Mesa-24.0
A change merged today for Mesa 24.0 is yielding much better Vulkan ray-tracing performance for the Radeon Vulkan driver 'RADV' across a number of games.
Kthat's our recommendation too, never manage it yourself, use WineZGUI for simple stuff, use Lutris for everything else
TI also don't know why I wrote that with wiggle room. I never recommend it
Teven simple stuff I open a dump site Bottle just to prevent poisoning of a prefix
CFound a typo in the buzz:
Cand another one :S :
Till fix that
C
Cuh
Kujust is correct
