gtk-doc: 1.30 -> 1.29 #62079
Merged
gtk-doc: 1.30 -> 1.29 #62079
Conversation
This file contains 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
This reverts commit 0e27680. Let's revert the gtk-doc update for now; it causes too many problems.
This reverts commit 064ca0a. The previous gtk-doc version won't build with our current meson.
This reverts commit 765079f. Problems, usually around https://gitlab.gnome.org/GNOME/gtk-doc/issues/84
This reverts commit dae72e7. Not needed now.
This reverts commit 7c62ef8. Not needed now.
|
Tested and it works. |
|
After looking at how Additionally |
Closed
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.
There are far too many problems on staging-next and no benefits I know of; see e.g. around #61657 (comment)
It's almost the state from nixpkgs master, but to be sure, I tested building stuff like libpsl, libical, glib.