use of <suggests> in modulesets is confused
@desrt
Submitted by Allison Karlitskaya Link to original bug (#693290)
Description
We use <suggests>
like so:
<autotools id="glib">
...
<suggests>
</suggests>
</autotools>
as if it somehow means "these things should be built after building glib".
It doesn't mean that at all, though.
'jhbuild build --build-optional-modules glib' just builds glib and its dependencies (and --build-optional-modules is the only argument listed in --help that says anything about suggests or 'soft depends').
Meanwhile, another module uses it in a way that seems to mean "this would be nice to have to enable optional features during my build":
<autotools id="libchamplain">
...
<suggests>
</suggests>
</autotools>
When building that module, --build-optional-modules has no effect on the number of packages built (vs. giving no arguments), but --ignore-suggests results in the suggests packages being ignored.
I guess this probably means that glib is the example of invalid usage (and that I don't understand what --build-optional-modules is supposed to do, unless it overrides a config file saying the opposite).
Outside of glib, it appears that the only module using <suggests>
in a way that introduces cyclic dependencies is gnome-js-common suggesting seed.