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

Drop fixxref from gtk-doc #611

Closed
wants to merge 1 commit into from

Conversation

yselkowitz
Copy link

GLib 2.79.0 switched from gtk-doc to gi-docgen, whose format and installation location are both not compatible. This allows the docs to build with the latest GLib at the price of some broken links.

This fixes the F40FTBFS from the mass rebuild.

GLib 2.79.0 switched from gtk-doc to gi-docgen, whose format and
installation location are both not compatible.  This allows the docs to
build with the latest GLib at the price of some broken links.
@ppisar ppisar self-assigned this Jan 26, 2024
@ppisar
Copy link
Collaborator

ppisar commented Jan 26, 2024

Thanks for the patch. I will try to make the fixxref optional not to regress libmodulemd documentation for people with old glib2 < 2.79.0.

I'm also considering to refer to new locations in glib2 ≥ 2.79.0 because they keep providing *.devhelp2 indices which gtkdoc-fixxref uses for rewriting the links. Though, I briefly checked /usr/share/doc/glib-2.0/glib/glib.devhelp2 and it is missing entries for such basic types as gchar. For other, like struct GError, it uses a shorter "GError" identifier. So I'm still not persuaded to utilize the new locations.

@ppisar
Copy link
Collaborator

ppisar commented Jan 26, 2024

When using the new path, not a single reference to glib and gobject is resolved.

ppisar added a commit to ppisar/libmodulemd that referenced this pull request Jan 26, 2024
GLib 2.79.0 switched from gtk-doc to gi-docgen, whose format and
installation location are both not compatible. The libmodulemd build
script reported an error because of the new location.

This patch fixes the build failure by using the new location if GLib
is 2.79.0 or greater.

Although the libmodulemd documentation references to GLib remain
unresolved now (i.e. names of the functions and the types are not
hyperlinks), we keep using the new location because the new GLib
*.devhelp2 indices remain there and they can only improve over the
time.

If this expection does not fulfill, libmodulemd will either migrate to
gi-docgen, or drop the hard build-time dependency on GLib
documentation.

Reimplements: fedora-modularity#611
ppisar added a commit to ppisar/libmodulemd that referenced this pull request Jan 26, 2024
GLib 2.79.0 switched from gtk-doc to gi-docgen, whose format and
installation location are both not compatible. The libmodulemd build
script reported an error because of the new location.

This patch fixes the build failure by using the new location if GLib
is 2.79.0 or greater.

Although the libmodulemd documentation references to GLib remain
unresolved now (i.e. names of the functions and the types are not
hyperlinks), we keep using the new location because the new GLib
*.devhelp2 indices remain there and they can only improve over the
time.

If this expection does not fulfill, libmodulemd will either migrate to
gi-docgen, or drop the hard build-time dependency on GLib
documentation.

Reimplements: fedora-modularity#611
@sgallagher
Copy link
Collaborator

Closing in favor of #612

@sgallagher sgallagher closed this Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants