From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Encouraging distros to use newer recipe versions?
Date: Sat, 06 Mar 2010 07:10:40 -0800 [thread overview]
Message-ID: <1267888240.11175.32.camel@rex> (raw)
In-Reply-To: <4B926E27.4090100@mwester.net>
On Sat, 2010-03-06 at 09:00 -0600, Mike Westerhof wrote:
> Does it make any sense to create a class (or extend the sanity or
> testlab classes) so that OE can inform someone when a given build is
> using a recipe that can be considered obsolete? Perhaps we might also
> add a bit more encouragement if it were possible to have that same
> class call out builds that have selected versions with known security
> vulnerabilities.
>
> This would certainly help me with the distro I maintain -- one of the
> questions I cannot easily answer, and therefore tend to ignore, is
> "exactly how out-of-date has my distro become?".
>
> I have no patches to do such a thing, and neither do I have time to
> create such a thing at this point in time, but perhaps if someone
> thinks this is worthwhile time can be made for it...
I've been keeping half an eye on what Holger has been doing and yes, I
think this could be desirable. Its also rather straightforward to do.
Simply create a new variable
SECURITY_ISSUES_PRESENT = "This package has know security issues of: X,
Y, Z"
and then have insane.bbclass choke on this printing the messages unless
you set a variable ILOVESECURITYHOLES = "1"
:)
Cheers,
Richard
next prev parent reply other threads:[~2010-03-06 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 15:00 Encouraging distros to use newer recipe versions? Mike Westerhof
2010-03-06 15:10 ` Richard Purdie [this message]
2010-03-08 6:08 ` Holger Hans Peter Freyther
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=1267888240.11175.32.camel@rex \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.