Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

version: allow building with ancient libpsl #12872

Closed
wants to merge 2 commits into from
Closed

Conversation

bagder
Copy link
Member

@bagder bagder commented Feb 6, 2024

The psl_check_version_number() API was added in libpsl 0.11.0. CentOS 7 ships with version 0.7.0 which lacks this API. Revert to using the older versioning API if we detect an old libpsl version.

Follow-up to 72bd88a Bug: https://curl.se/mail/archive-2024-02/0004.html Reported-by: Scott Mutter

The psl_check_version_number() API was added in libpsl 0.11.0. CentOS 7
ships with version 0.7.0 which lacks this API. Revert to using the older
versioning API if we detect an old libpsl version.

Follow-up to 72bd88a
Bug: https://curl.se/mail/archive-2024-02/0004.html
Reported-by: Scott Mutter
@bagder bagder added the build label Feb 6, 2024
@bagder bagder closed this in 174c89e Feb 6, 2024
@bagder bagder deleted the bagder/old-libpsl branch February 6, 2024 08:51
@GrahamCampbell
Copy link
Contributor

Is allowing super old versions actually a good idea. Using an old PSL can be just as bad as using none at all?

@bagder
Copy link
Member Author

bagder commented Feb 8, 2024

This is actually just supporting the old API. I believe that old version of the lib can still be built using an updated database. But even so, I believe an outdated database is probably better than none at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

3 participants