From: Saul Wold <sgw@linux.intel.com>
To: akuster <akuster@mvista.com>,
OE-core <openembedded-core@lists.openembedded.org>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: /etc/os-release
Date: Mon, 14 Jul 2014 15:50:40 -0700 [thread overview]
Message-ID: <53C45EC0.6070801@linux.intel.com> (raw)
In-Reply-To: <53C45BD7.1020104@mvista.com>
On 07/14/2014 03:38 PM, akuster wrote:
> Hello all,
>
> I noticed some reference to /etc/os-release in some recipes. Where can I
> find the initial creation of /etc/os-release? If one is not created,
> would there desire to have one?
>
Really? We reference it in the meta/lib/oe/lsb.py release_dict_file()
function to search for LSB information of the host machine to identify
the host distro version information.
Can you be specific about which recipes are using os-release, I did do a
search.
Sau!
> regards,
> Armin
next prev parent reply other threads:[~2014-07-14 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 22:38 /etc/os-release akuster
2014-07-14 22:50 ` Saul Wold [this message]
2014-07-14 22:54 ` /etc/os-release Christopher Larson
2014-07-14 23:05 ` /etc/os-release akuster
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=53C45EC0.6070801@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=akuster@mvista.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.org \
/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