Introduce EXTRA_VERSION_PATCHES This allow third-party (packagers) to provide more information about what custom patches were applied to the tree. To do so, one can create emtpy files in "version/extra_patches/", the filenames will be used to generate the EXTRA_VERSION_PATCHES define. Add this information to the debug log of lttng-relayd and lttng-sessiond. Also append it at the end of the "version" command of the lttng binary. Signed-off-by: Jonathan Rajotte <jonathan.rajotte-julien@efficios.com> Signed-off-by: Michael Jeanson <mjeanson@efficios.com> Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Introduce EXTRA_VERSION_NAME and EXTRA_VERSION_DESCRIPTION On version.i generation, check the content of the following files : * "extra_version_name" The first line is used to populate the EXTRA_VERSION_NAME pre-processor define statement. * "extra_version_description" The content is used to populate the EXTRA_VERSION_DESCRIPTION pre-processor define statement. It should contain the description of local modifications done to the tree. This can be used by distribution packager to specify what changes were applied locally. Mostly in the form of patch/commit name. All non-alpha numeric characters are converted to "-". Signed-off-by: Jonathan Rajotte <jonathan.rajotte-julien@efficios.com> Signed-off-by: Michael Jeanson <mjeanson@efficios.com> Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>