After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 682761 - Add a build-essential systemmodule
Add a build-essential systemmodule
Status: RESOLVED OBSOLETE
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Jhbuild maintainers
Jhbuild QA
: 687717 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-08-27 05:37 UTC by Craig Keogh
Modified: 2021-05-17 15:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Craig Keogh 2012-08-27 05:37:10 UTC 
As recommended by Colin in bug 681342 comment 3, JHBuild could support a special systemmodule "build-essential". "build-essential" will automatically become a dependency of every module - no need to explicitly add <dep package="build-essential"/> to every module.

Or how about a special systemmodule for each modtype? For example "autotools-essential" that includes automake, autoconf, libtool, etc. "autotools-essential" is only applicable to <autotools> modules.
"cmake-essential" will have cmake. "waf-essential" will have waf, etc.

Or could do both?
Comment 1 Craig Keogh 2012-11-10 03:14:10 UTC 
*** Bug 687717 has been marked as a duplicate of this bug. ***
Comment 2 GNOME Infrastructure Team 2021-05-17 15:53:59 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/jhbuild/-/issues/137.