Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • evolution evolution
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 292
    • Issues 292
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • evolutionevolution
  • Issues
  • #196
Closed
Open
Created Oct 29, 2018 by Bernhard M. Wiedemann@bmwiedemann

Build developer documentation in a fix order

While working on reproducible builds for openSUSE, I found that when building the evolution package for openSUSE Tumbleweed, there were differences between each build in html files generated by gtk-doc.

Those are created in 5 dirs in 2 steps each.

The 1st step is gtkdoc-mkhtml and the 2nd step is gtkdoc-fixxref. And results there vary from racy parallelism (unless always building with -j1).

I tested that when dropping the fixxref part, results become reproducible.

I think, the 5 fixxref steps should only run after all 5 gtkdoc-mkhtml steps are done, which is currently not the case.

Example package-diff

Edited Oct 30, 2018 by Milan Crha
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking