feat: permit use of system rapidyaml#1305
Merged
johnbartholomew merged 1 commit intogoogle:masterfrom Mar 9, 2026
Merged
Conversation
Collaborator
|
I think this probably won't work as-is on Debian, because the libryml-dev package doesn't contain any CMake package config (or even any pkg-config files!): https://packages.debian.org/sid/amd64/libryml-dev/filelist Might just be a Debian packaging problem, I'm not certain. |
Signed-off-by: Pat Riehecky <riehecky@fnal.gov>
Contributor
Author
|
I'll confess, I'm mostly working on Fedora/RHEL which provide: |
Collaborator
|
Ok. Let's assume Debian packaging will catch up eventually. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This addresses the TODO to permit use of the system rapidyaml rather than the vendored files.
In theory this should make packaging a bit more consistent across various build environments.
I'd love to see this in 0.22.0