1 The jhbuild module consists of a package build framework, and a number
2 of configuration files for building various Gnome releases. The rules
3 for checkins differ for each.
5 Modifications to the build framework should be submitted as bug
6 reports at http://bugzilla.gnome.org/ where they can be reviewed
7 before being committed. The exception to this is build sheriff style
8 commits for small errors that prevent people from using jhbuild. When
9 in doubt, submit a bug report.
11 The modulesets/ directory contains configuration files that describe
12 how to build various versions of Gnome. The file gnomeXY.modules
13 contains rules needed to build the stable version X.Y of Gnome or the
14 development branch leading up to that version. Changes of the
15 following types can be committed without approval:
17 - Updating the branch tag for a module if it is incorrect for that
20 - Updating to a new version of a tarball for tarball type
21 defintions, provided the new version is appropriate for that Gnome
24 - Adding a definition for a module that is part of the Gnome desktop,
25 developer platform, 5th toe or bindings release, etc, but is
26 missing from the module set.
28 - Removal of module definitions where the associated module has been
29 removed/obsoleted from the particular Gnome version (eg. acme was
30 removed from gnome26 when it got integrated into control-center).
32 A number of modules that fall outside of a Gnome release but are
33 related to Gnome are also included in the module set. This includes
34 software that may be under development and not ready for general use.
36 If you would like to add a module to one of the standard module sets,
37 submit a bug report as detailed above. If it is Gnome related, it
38 will probably get accepted.
40 If your module is not Gnome related, it may get rejected. Keep in
41 mind that jhbuild supports external module sets that are identified by
42 a full URI, which allows third parties to maintain module sets