From: richard.purdie@linuxfoundation.org
To: akuster808 <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] os-release: add more variables to list
Date: Mon, 29 Oct 2018 21:10:13 +0000 [thread overview]
Message-ID: <3fb4ca4995bbf08a40eebfa07518b6ffe2d99855.camel@linuxfoundation.org> (raw)
In-Reply-To: <80df3fff-2347-4736-758c-5050ac31494f@gmail.com>
On Mon, 2018-10-29 at 12:36 -0700, akuster808 wrote:
> On 10/29/18 10:12 AM, richard.purdie@linuxfoundation.org wrote:
> > This sounds very much like "I want to be a distro but I don't want
> > to
> > be a distro".
> >
> > Changing os-release just because a layer was included is a really
> > bad
> > idea. Its distro policy what would be included there, including
> > what
> > the cpe name might be.
>
> This is why I think its appropriate to have at least "CPE_NAME"
> added.
> >
> > Whether the nodistro defaults are right is a different question but
> > meta-security should not be poking there.
>
> I really didn't want to do another layer for something as simple as
> "CPE_NAME" but why not.
Does OE have a standard "CPE_NAME" which works for everything/everyone?
Should it have?
I get the feeling I'm missing something here but you're not giving me
much to work with and the original patch didn't just add CPE_NAME...
Cheers,
Richard
prev parent reply other threads:[~2018-10-29 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 7:20 [PATCH] os-release: add more variables to list Armin Kuster
2018-10-25 9:25 ` Richard Purdie
2018-10-28 18:24 ` akuster808
2018-10-29 17:12 ` richard.purdie
2018-10-29 19:36 ` akuster808
2018-10-29 21:10 ` richard.purdie [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=3fb4ca4995bbf08a40eebfa07518b6ffe2d99855.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.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