![]() Only dependencies required for gedit are included and the resulting files are written to disk. Merges all modules into two moduleset files (bootstrap.modules and gedit.modules). ![]() For all GNOME modules, checks if there are newer versions available (stable or unstable), and asks whether or not to update modules that are out of date.This makes it easy to spot whether a given override is now out of date, or needs to be updated (for example with additional patches). For modules that already exist, a diff is shown and the user is asked whether or not to update the module from the overrides file. Applies our own specific overrides and additional modules from a separate overrides file.To make updating and maintaining the moduleset easier, we now have a tool which: This too improves build reproducibility by fixing all dependencies to specific versions. We now also distribute our complete jhbuild moduleset in-tree so that we no longer rely on a possibly moving external moduleset source. This makes the entire build more reliable, independent and reproducible. Importantly, whereas before we would use a jhbuild already setup by the user, we now install and configure jhbuild entirely in-tree and independently of existing jhbuild installations. All of the individual phases are commands which can be invoked by build separately if needed. The build script downloads and installs jhbuild (if needed), configures it with the right environment for gedit, bootstraps and finally builds gedit. There is a single entry point (osx/build/build) which is basically a wrapper around jhbuild (and some more). ![]() We are still using jhbuild as before, but have automated all of the previously manual steps (such as installing and configuring jhbuild).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |