@Dennis Which Fedora version should be targeted while providing rpms with language implementation?

@AmokHuginnsson 29, but ideally you wouldn't target a specific Fedora or even a specific rpm-based distro

@Pavel 29 had EOL on 2019-11-26

@Pavel isn't it easier to ensure the language implementation installs properly if I target specific distro version while building RPMs?

@AmokHuginnsson yes but that's what TIO's running

@AmokHuginnsson No because it means it's harder to upgrade to a newer version

@Pavel harder for whom?

For Dennis

@Pavel thank you. I am still not sure what it means to not target specific version while building RPMs though :)

@AmokHuginnsson Also, for TIO, just don't provide an rpm. A tarball is better.

@Pavel I already provide RPMs for TIO.

¯\_(ツ)_/¯

I just learned how out of date my builder was.

I'm not Dennis, I just know that TIO currently runs on Fedora 29

Hence the questions.

I also know that in the future it will eventually not run on 29

@Pavel by tarball you mean source version or prebuilt binaries?

Either one, binaries are probably better?

Well, that would require static linking, doable but flaky.

:-/

Thank you for important bit of information anyway :)

Oh, do you have some extra dependencies

@Pavel yes, my implementation links to a bunch of libraries.

Those can probably just be installed onto TIO depending on what they are specifically but source would likely be fine too

It seems to me that the easiest route is still to just build it for Fedora 29 ;)

Then it should just work™