From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] support/scripts/setlocalversion: ignore user settings for Mercurial
Date: Mon, 18 Feb 2019 17:13:26 +0100 [thread overview]
Message-ID: <8736olaxcp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190130201508.10304-2-patrickdepinguin@gmail.com> (Thomas De Schampheleire's message of "Wed, 30 Jan 2019 21:15:08 +0100")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
> From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> setlocalversion will use 'hg id' to determine whether or not the current
> revision is tagged. If there is no tag, the Mercurial revision is printed,
> otherwise nothing is printed.
> The problem is that the user may have custom configuration settings (in
> their ~/.hgrc file or similar) that changes the output of 'hg id' in a way
> that the script does not expect. In such cases, the Mercurial revision may
> not be printed or printed incorrectly.
> It is good practice to ignore the user environment when calling Mercurial
> commands from a well-defined script, by setting the environment variable
> HGRCPATH to the empty string. See also 'hg help environment'.
> In the particular case of Nokia, a custom extension adds dynamic tags in the
> repository, i.e. tags that are stored in a file external to the repository
> and only visible when the extension is active. These tags should not
> influence the behavior of setlocalversion as they are not official Buildroot
> tags, i.e. even if a revision is tagged, the Mercurial revision should still
> be printed.
> Note that this still does not solve the problem where an organization adds
> _real_ tags in their Buildroot repository. For example, there might be a
> moving tag 'last-validated' or tags indicating in which product release that
> Buildroot revision was used. In these cases, setlocalversion will still not
> behave as expected, i.e. show the Mercurial revision.
> Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Committed to 2018.02.x and 2018.11.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-02-18 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 20:15 [Buildroot] [PATCH 1/2] support/scripts/setlocalversion: fix detection of hg revision when _not_ on branch 'default' Thomas De Schampheleire
2019-01-30 20:15 ` [Buildroot] [PATCH 2/2] support/scripts/setlocalversion: ignore user settings for Mercurial Thomas De Schampheleire
2019-02-18 16:13 ` Peter Korsgaard [this message]
2019-02-04 20:24 ` [Buildroot] [PATCH 1/2] support/scripts/setlocalversion: fix detection of hg revision when _not_ on branch 'default' Thomas Petazzoni
2019-02-18 16:13 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736olaxcp.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox