GNOME Bugzilla – Bug 775933
Only buildone for some modules
Last modified: 2016-12-10 21:19:33 UTC
Why some modules have "info" et can be "build" whereas some can only be "buildone" ? Example with geary : jhbuild info geary doesn't work jhbuild build geary doesn't work jhbuild buildone geary works It's very confusing when you discover that. Those special modules should have a special output for "info" and "build".
It's because we don't have a JHBuild module for geary: it's not part of GNOME releases. (We used to have it in gnome-world, but I removed it because it still depends on WebKit1; we can put it back once that changes.) Anyway, look at what's happening: $ jhbuild buildone geary I: module "geary" does not exist, created automatically using repository "git.gnome.org" So looks like JHBuild is able to automatically buildone any Autotools module on git.gnome.org (notice that the Geary build fails pretty badly trying to execute configure ;) including modules that aren't defined in the JHBuild modulesets. I can see how that might be confusing (I didn't know about it until just now) but I don't see what to do about it; it doesn't seem useful to remove that behavior. There's no way we can make 'jhbuild build' work because there is no JHBuild module for Geary and thus no dependency information. So I don't think there's anything to be done here; unless you have some specific suggestion, I'm going to close this NOTABUG.
Thx a lot for your fast answer. I follow my remark to geary wiki at https://bugzilla.gnome.org/show_bug.cgi?id=775215#c2