Orphaned rubygem-fast_gettext
by Vít Ondruch
Hi,
I have orphaned rubygem-fast_gettext, because I have no use for it,
neither anything else depends on it.
VĂt
3 years, 8 months
Re: How do Fedora developers get access to devtoolset for testing.
by Steven Munroe
Dave Love; writes:
...
> I'm pretty sure I said to do that a while ago, like I did when
> testing the trivial patch that I didn't expect to cause such trouble.
You probably did say so ;)
I come from a different culture and experience. I am not as conversant
in Fedorian as I should be. So I tend to misunderstand what is plain
to you all.
From my experience, installing (something like) devtoolset on Fedora
was not an outlandish idea, Apparently it is.
So installing a centos 7 VM instance on my local power8 seems like a
better option.
Thanks
3 years, 8 months
diffmark license corrected
by Petr Pisar
I corrected diffmark license from "diffmark and GPLv2+ and (GPL+ or Artistic)"
to "diffmark and (GPL+ or Artistic)".
-- Petr
3 years, 8 months
F33 Change proposal: DXVK as default wined3d backend on VK capable
hardware (Self-Contained Change)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/DXVKwined3d
== Summary ==
Proposal to replace default wined3d backend with DXVK, A Vulkan-based
translation layer for Direct3D 9/10/11 which allows running 3D applications
on Linux using Wine.
Currently, wine in Fedora uses wined3d and users can optionally install
DXVK (be it wine-dxvk package or by any other means). With this change
accepted, wine would use DXVK instead of wined3d on supported GPUs
automatically.
== Owner ==
* Name: [[User:frantisekz| Frantisek Zatloukal]]
* Email: fzatlouk(a)redhat.com
== Detailed Description ==
DXVK is an alternative to wined3d providing more performant and more
compatible way to run Windows applications and games using DirectX 9, 10
and 11.
More detailed description is available on [https://github.com/doitsujin/dxvk
DXVK Github].
DXVK is available as a wine-dxvk package since Fedora 31. wine-dxvk package
uses alternatives system for following wine dll files: d3d9, d3d10.dll and
d3d11.dll .
Should this proposal be accepted, [
https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4# a Pull
Request] will be merged into the wine-dxvk package which ensures it gets
set as default backend only on systems with Vulkan support. wine-dxvk will
then get added as "Recommends: wine-dxvk" into the wine package itself.
Users can run 'dnf reinstall wine-dxvk' after changing hardware
configuration to get alternatives to use DXVK or wined3d updated.
This proposal can be accepted in a "reduced form" of replacing the default
wined3d backend only for DirectX 10 and 11 and leaving DirectX 9 to be
handled by the current wined3d.
== Benefit to Fedora ==
Fedora users running recent Windows games will get superior performance and
compatibility. Steam already leverages DXVK but there are other Game Stores
and standalone games which would benefit from DXVK. Users had to know about
this project and install it manually (or use e.g. Lutris), whereas having
DXVK included by default will make sure everybody gets the best possible
performance and compatibility.
I haven't done benchmarking per se, there are multiple resources on the
Internet comparing DXVK and wined3d. If necessary I will do additional
testing on my hardware in the week of July 27th.
== Scope ==
* Proposal owners: Merge
https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4# ; add
Recommends: wine-dxvk into wine the package.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
The aim is to convert users with supported Hardware Configuration to DXVK
as a part of Fedora 32 > Fedora 33 upgrade. There should not be any
breakage since postinst script of wine-dxvk package would verify if the GPU
supports Vulkan or not and set alternatives to wined3d or DXVK accordingly.
There is a slight possibility of user experience degradation compared to
wined3d on old Intel iGPUs supporting just a subset of Vulkan specification
(Ivy Bridge and Haswell generations). I haven't had any opportunity to test
DXVK on such hardware, however, if issues are discovered, check for Vulkan
from wine-dxvk package PR (
https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4#_1__26 ) could
be improved to block certain GPU vendors/generations/models.
AMD and/or nVidia GPUs should not be affected, they either do not support
Vulkan at all, or they support it fully.
On GPUs without Vulkan support, wine-dxvk would remain installed and
unused, consuming about 167 MB of HDD space. Users would be able to opt-out
from using DXVK by adding 'exclude=wine-dxvk*' into /etc/dnf/dnf.conf and
removing wine-dxvk package.
== How To Test ==
1. Make sure you have Vulkan compatible GPU ('vulkaninfo' runs without
errors)
2. Install wine-dxvk package
3. Run some Windows game with wine
A testday will take place before Fedora 33 GA to determine and workaround
(disable DXVK and fallback to wined3d) issues on potentially broken
hardware and GPU drivers.
In cases when something worked before installing wine-dxvk and stopped
after (or regressed), bugs should be reported to [
https://github.com/doitsujin/dxvk/issues DXVK Issue Tracker].
== User Experience ==
(not provided)
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: Obsolete wine-dxvk through base wine package
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? No
* Blocks product? No
== Documentation ==
N/A (not a System Wide Change)
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 8 months
Re: How do Fedora developers get access to devtoolset for testing.
by Steven Munroe
Dave Love writes:
> It surprises me if that's IBM experience, and it's a bit worrying for our
new system.
I no longer speak for IBM (retired) so more of a personal Linux for POWER
opinion. But the Advance Toolchain (AT)
<ftp://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/...>
provides
the counter example and as it's on the 13th release (follows GCC releases,
AT14 coming soon) I would say useful and valid. AT does separate builds for
each distro it supports but the RHEL 8 build, installs on Fedora.
Full disclosure, AT was my idea. The goal was to enable new POWER hardware
feature for customers, who insisted on running old (stable) distributions.
Now it is likely DevToolSet has different and conflicting goals. I am
willing to accept that and move on.
> Really, it isn't necessary, any more than it was for me on the Fedora
development system.
Well it is, as PVECLIB supports BE and LE. And a chroot will not handle
that.
3 years, 8 months