Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster <akuster@mvista.com>
To: Christopher Larson <clarson@kergoth.com>,
	Saul Wold <sgw@linux.intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: /etc/os-release
Date: Mon, 14 Jul 2014 16:05:52 -0700	[thread overview]
Message-ID: <53C46250.4070905@mvista.com> (raw)
In-Reply-To: <CABcZANkqBZ3Kw7POOBYQ-1=6rxZSioakS-K7qbS2CcYvp1C_xg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]

Chris,

On 07/14/2014 03:54 PM, Christopher Larson wrote:
> On Mon, Jul 14, 2014 at 3:50 PM, Saul Wold <sgw@linux.intel.com 
> <mailto:sgw@linux.intel.com>> wrote:
>
>     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.
>
>
> I'm pretty sure we don't have an os-release recipe in oe-core at all 
> yet, so the file isn't going to exist on target. Mentor has one in 
> meta-mentor at the moment pending time to submit it again / poke on 
> the existing thread. See the thread with the subject "[RFC PATCH 0/2] 
> Add /etc/os-release". It's definitely something we should have, in my 
> opinion.
Yeah, That is what I was thinking of.
Thanks for the pointer.

- Armin

> -- 
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics


[-- Attachment #2: Type: text/html, Size: 3083 bytes --]

      reply	other threads:[~2014-07-14 23:05 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 ` /etc/os-release Saul Wold
2014-07-14 22:54   ` /etc/os-release Christopher Larson
2014-07-14 23:05     ` akuster [this message]

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=53C46250.4070905@mvista.com \
    --to=akuster@mvista.com \
    --cc=clarson@kergoth.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    --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