Commit 5f83ef99 authored by Thomas Haller's avatar Thomas Haller
Browse files

build: drop internal field __nm_git_sha from libraries

The problem is that you cannot be sure which patches
were applied on top of a source tree, so the __nm_git_sha
value is unreliable.

Also, after running autoreconf during the package build,
NM_GIT_SHA is reset as well.
parent 3b6fc5cb
......@@ -45,9 +45,6 @@
#include "nm-setting-wired.h"
#include "nm-setting-wireless.h"
/* Embed the commit id in the build binary */
static const char *const __nm_git_sha = NM_STRLEN (NM_GIT_SHA) > 0 ? "NM_GIT_SHA:"NM_GIT_SHA : "";
/**
* SECTION:nm-utils
* @short_description: Utility functions
......@@ -223,8 +220,6 @@ _nm_utils_init (void)
GModule *self;
gpointer func;
(void) __nm_git_sha;
if (initialized)
return;
initialized = TRUE;
......
......@@ -37,9 +37,6 @@
#include "nm-setting-private.h"
#include "crypto.h"
/* Embed the commit id in the build binary */
static const char *const __nm_git_sha = NM_STRLEN (NM_GIT_SHA) > 0 ? "NM_GIT_SHA:"NM_GIT_SHA : "";
/**
* SECTION:nm-utils
* @short_description: Utility functions
......@@ -234,8 +231,6 @@ static gboolean initialized = FALSE;
gboolean
nm_utils_init (GError **error)
{
(void) __nm_git_sha;
if (!initialized) {
initialized = TRUE;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment