The git:// protocol is problematic from a security perspective, as
it provides no authenticity of data. https:// also works better in
environments with restricted network connectivity.
Also add CLONE_OPTS to do shallow checkouts more easily.
https://bugzilla.gnome.org/show_bug.cgi?id=775110
Use grep -o to grab the log message only. This makes it work with colored log
files too. Prefilter the log to not catch tracer classes.
Update the commandline for the script in the docs.
The git-update.sh now builds with all cores available. In case of
failure it defaults to 1
The developer can still override this by setting -j to something else
in MAKEFLAGS, as stated by 299605dfe2.
https://bugzilla.gnome.org/show_bug.cgi?id=766666
Some OpenCV plugins use haar cascade files that are included in the
GStreamer sources. To be able to use these from uninstalled, they need
to be found through an environment variable.
Adding this environment variable pointing to haar cascade files to
gst-uninstalled.
This reverts commit ab5fdd7212.
We can use the MAKEFLAGS environment variable to pass options to make,
so avoid adding another mechanism that could be confusing.
Error out if required build tools (flex, bison, pkg-config)
are not present, instead of printing a message and then
continuing.
Check out submodules when fetching the repositories, so
they're already there and ready later.
Remove some 0.10 cruft.
Add more git repositories to check (so git-version.sh is consistent with
gst-uninstalled) and display the date of the last commit, which is more valuable
information than the last commit's hash.
For some rare cases, one might not be able to use the hardcoded $HOME/gst
location yet would still want to use the gst-uninstalled script as-is (which
has the benefit of being constantly updated).
For these cases, the checkout directory can be specified with the
GST_UNINSTALLED_ROOT environment variable.
Ex:
export GST_UNINSTALLED_ROOT=$HOME/somewhere/with/checkouts
And then just call gst-uninstalled directly:
$GST_UNINSTALLED_ROOT/gstreamer/gst-uninstalled
By default when the script is about to exit (normally or due to an error),
it checks whether $ERROR_LOG file exists. If the log file exists, the
script prints a "Failures: " message prefix and dumps the log file to the
output.
Apparently the log file is always created and if the update/build is
successful, the script finishes with a bit misleading "Failures: " message.
An improvement provided with this change lets the log file to be created as
needed, i.e. if there's an error message to be printed. If the file
doesn't exists, the script prints a "Update done" message which clearly
indicates success.
https://bugzilla.gnome.org/show_bug.cgi?id=701177
