Bug 745003 – Warn if bootstrap recipes have been updated

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 745003 - Warn if bootstrap recipes have been updated


Summary:	Warn if bootstrap recipes have been updated


Status:	RESOLVED OBSOLETE

Product:	GStreamer
Classification:	Platform
Component:	cerbero
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	git master
Assigned To:	GStreamer Maintainers
QA Contact:	GStreamer Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2015-02-23 10:27 UTC by Nirbheek Chauhan
Modified:	2018-11-03 10:18 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Nirbheek Chauhan 2015-02-23 10:27:07 UTC

While building a recipe for a particular config, Cerbero should warn if:

a) Bootstrap hasn't been done or
b) Bootstrap recipes have been updated and bootstrap should be re-run

Otherwise people will continue to have build problems even after they've been fixed in build-tools recipes.

Comment 1 Edward Hervey 2015-02-23 13:07:42 UTC

Just always run 'bootstrap --build-tools-only'

If there's no updates => takes a second
If there are updates => it'll rebuild them

Or should we always run bootstrap --build-tools-only when building recipes ?

Comment 2 Nirbheek Chauhan 2015-02-23 13:12:23 UTC

One alternative is to spew a warning asking the user to run it when the cache says the build-tools have an update available. Less automagic is usually better. Don't want, for instance, a build problem with bootstrap build tools to block all recipe building. :)

Comment 3 GStreamer system administrator 2018-11-03 10:18:30 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org'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.freedesktop.org/gstreamer/cerbero/issues/10.