Skip to content
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.

Adds Fedora 36 and 37 build targets #135

Closed
wants to merge 0 commits into from
Closed

Adds Fedora 36 and 37 build targets #135

wants to merge 0 commits into from

Conversation

innovara
Copy link
Contributor

It is possible to build wkhtmltopdf for Fedora 36 and 37 with the changes included in this commit.

Tested for x86_64 and aarch64 builds.

Copy link
Member

@ashkulz ashkulz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@innovara also, you should use the 0.12.6.x branch for making builds -- I think I pointed it out in the other issue.

Also, is there any reason to support Fedora 36? My understanding is that people on Fedora tend to upgrade regularly, plus it's not an LTS distribution 🤷‍♂️

openssl-devel \
perl \
zlib-devel \
qtwebkit-devel \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you need this? If not for this package, you could use Dockerfile.centos as-is (I think yum is still supported on Fedora, right?).

If this pulls in packages which are required, I'd want them to be explicitly listed instead of qtwebkit-devel.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you need this? If not for this package, you could use Dockerfile.centos as-is (I think yum is still supported on Fedora, right?).

In fact, it's not needed. I thought it solved a problem when compiling qt but that's not the case.

Regarding using yum in Fedora, yes, you can use it. Currently /usr/bin/yum is a symbolic link to dnf-3, same as /usr/bin/dnf

If this pulls in packages which are required, I'd want them to be explicitly listed instead of qtwebkit-devel.

qtwebkit-devel requires qt-devel but it is not needed anyway.

@innovara innovara closed this Dec 28, 2022
@innovara
Copy link
Contributor Author

@innovara also, you should use the 0.12.6.x branch for making builds -- I think I pointed it out in the other issue.

Noted, thanks. I see that the 0.12.6.x branch is 1 commit ahead and 31 behind the master. I don't know to what extent it would be recommendable to bring some of those changes to it.

Also, is there any reason to support Fedora 36? My understanding is that people on Fedora tend to upgrade regularly, plus it's not an LTS distribution man_shrugging

Not really. Fedora 36's EOL is in May 2023. I just thought that if it compiles, why not? It might be of some use to someone...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants