From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/next] Makefile: use /etc/os-release for version info rather than /etc/br-version
Date: Tue, 14 Feb 2012 17:07:52 +0100 [thread overview]
Message-ID: <4F3A86D8.5010605@lucaceresoli.net> (raw)
In-Reply-To: <20120214121000.DDC1090A9E@busybox.osuosl.org>
Peter Korsgaard wrote:
> commit: http://git.buildroot.net/buildroot/commit/?id=451a887894faddef019e9a0628c21b5f2e9eee56
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/next
>
> /etc/os-release is becoming a standard interface for distribution
> name/version info, so let's use that instead of the nonstandard
> /etc/br-version. Format of the file is something like:
>
> NAME=Buildroot
> VERSION=2012.02-rc1-00003-g2d10e81
> ID=buildroot
> VERSION_ID=2012.02-rc1
> PRETTY_NAME="Buildroot 2012.02-rc1"
Nice.
I just wish PRETTY_NAME had at least a "-dirty" suffix to make it
clear that it is not exactly equal to 2012.02-rc1 (at least when using
a git clone).
Luca
next prev parent reply other threads:[~2012-02-14 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 12:08 [Buildroot] [git commit branch/next] Makefile: use /etc/os-release for version info rather than /etc/br-version Peter Korsgaard
2012-02-14 16:07 ` Luca Ceresoli [this message]
2012-02-14 16:18 ` 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=4F3A86D8.5010605@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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