On Sat, 29 Oct 2022 01:36:16 -0700
ToddAndMargo via users <users(a)lists.fedoraproject.org> wrote:
On 10/29/22 01:30, Samuel Sieb wrote:
> On 10/29/22 01:19, ToddAndMargo via users wrote:
>> Hi All,
>>
>> I have to dig out Wine version 6 from Fedora 35's
>> repo (Wine 7 is an absolute disaster).
>>
>> Question: how long will I be able to use the
>> dnf's `--releasever=35` option? How long are
>> the defunct repo's maintained?
>
> They aren't defunct. The files are eventually moved to archive and
> the mirror manager is reconfigured to point there. So there are
> less active mirrors for the content, but you can still access all
> the way back to Fedora Core 1.
With `--releasever` or do I have to get fancy?
As Samuel said, that should work, because the usage is so low that it
just picks it up from the archive by treating it as a repo. But,
eventually library incompatibilities will show up, because every new
version of Fedora has underlying changes that move it further away from
the original Fedora you are trying to import from. Your best bet is to
use the src.rpm, and tweak the dependencies, and build it locally so it
picks up later versions. That will last longer, but eventually it will
require code changes in order to build with newer libraries, so you
will become, to some extent, a source code maintainer for wine.
I think you could build a specific wine version in a container with its
dependencies, and as long as it runs on the same processor architecture,
it should not need to be updated. But, my knowledge of containers is
miniscule, so I could be wrong. It might make calls to the underlying
system libraries, or the container interface could change. Maybe just
rebuilding the container would take care of those, though. There have
been applications that have gone obsolete in the past that I wanted to
hang onto, that I considered this, but in the end I just moved to a
currently packaged substitute because of the work involved. I needed
the pulseaudio-equalizer but it went obsolete with the python2
retirement. I tweaked and built locally, but it became just too
much with library changes, and fortunately pipewire arrived with
easyeffects and its equalizer.
Another alternative would be to freeze an older system with the
configuration you want, keep it offline except when you need its
functionality, and have a current system for everything else. When you
need it, connect and share it via something like ssh, and run what you
need on that system, and bring the results back to the current system
when done.