Guoguo has quit [Remote host closed the connection]
Guoguo has joined #fedora-riscv
Guoguo has quit [Ping timeout: 264 seconds]
Guoguo has joined #fedora-riscv
Guoguo has quit [Remote host closed the connection]
Guoguo has joined #fedora-riscv
Guoguo has quit [Ping timeout: 264 seconds]
Guoguo has joined #fedora-riscv
Guoguo has quit [Ping timeout: 246 seconds]
Guoguo has joined #fedora-riscv
Guoguo has quit [Remote host closed the connection]
Guoguo has joined #fedora-riscv
Guoguo has quit [Ping timeout: 256 seconds]
davidlt has joined #fedora-riscv
davidlt has quit [Ping timeout: 264 seconds]
Guoguo has joined #fedora-riscv
Guoguo has quit [Ping timeout: 246 seconds]
Guoguo has joined #fedora-riscv
Guoguo_ has joined #fedora-riscv
Guoguo has quit [Ping timeout: 268 seconds]
Guoguo_ has quit [Ping timeout: 264 seconds]
Guoguo has joined #fedora-riscv
davidlt has joined #fedora-riscv
<davidlt>
rwmjones_, how to those students choose what to upstream to dist-git?
<davidlt>
and things like "ExclusiveArch:" are almost the last on my list
<davidlt>
rwmjones_, do you want be ACK/LGTM on all PRs? Otherwise I just plan to comment if there is anything that I would like to see changed, etc.
<davidlt>
All changes should go into Rawhide and then F40, and should have a new NVR.
<davidlt>
otherwise we not gonna see benefits for months, and it will be hard to track things too.
<rwmjones_>
morning
<davidlt>
I almost done looking at all PRs
<rwmjones_>
david: I don't know, best to ask fuwei
<rwmjones_>
I added comments about things I *don't* like in the PRs, that's all
<rwmjones_>
was going to leave the good ones to be reviewed by the packagers
<davidlt>
Could they squash all the suffix commits, etc?
<rwmjones_>
I can bump NVRs (in Fedora) for any package in Fedora, just let me know which one - I mean by this, not make any changes other than bump release and rebuild
<rwmjones_>
yes the suffix Release changes are all wrong, I think I said that on the ones I noticed
<davidlt>
If we commit changes without NVR + Changelog entry the maintainer might sit on the change, and not submit a build.
<davidlt>
We want to see a build with riscv change as soon as appropriate.
<sorear>
would "wine support for riscv64" mean integrating it with fex/box64, wine support for IMAGE_FILE_MACHINE_RISCV64, or winelib support for __riscv?
Guoguo has joined #fedora-riscv
Guoguo has quit [Remote host closed the connection]
<rwmjones_>
the way I understand how wine works, I don't understand how it can just run on riscv64
<davidlt>
rwmjones_, ah, this is similar to meson issue
<sorear>
I have a weak understanding of how wine works but much less of how it's packaged
<sorear>
if I have x86 or x86_64 Windows binaries and I want to run them on an aarch64 Fedora host, can I install the wine package and use that to drive the whole process or I do I need to separately install an emulator?
<sorear>
there's no NT RV64 ABI as of yet but there's a use case for running x86 binaries, however that's done
<rwmjones_>
sorear: I've not tried that, but typically it wouldn't work unless there's some emulation going on (like qemu-aarch64)
<rwmjones_>
typically (on x86-64) the binaries run directly and link to the wine library and talk to the separate wine-server
<rwmjones_>
with the wine-server making system calls on behalf of the windows binary
<rwmjones_>
I think they talk over a unix domain socket
<davidlt>
I think you can use win on aarch64 and run x86_64 games
<davidlt>
and, IIRC, Game Porting Toolkit (from Apple) is using Wine too