All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Hans Peter Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Encouraging distros to use newer recipe versions?
Date: Mon, 8 Mar 2010 07:08:11 +0100	[thread overview]
Message-ID: <201003080708.11546.holger+oe@freyther.de> (raw)
In-Reply-To: <1267888240.11175.32.camel@rex>

On Saturday 06 March 2010 16:10:40 Richard Purdie wrote:

> > 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


Such a class does make sense but is only fixing 50% of the issue. E.g. when we 
look at "gpdf" there are two things.

1.) The distro builder should be informed that building gpdf is bad in regard 
to known security issues. So he might decide to throw it out of the feed.

2.) A user using the distro has the (discontinued) package still installed and 
he will not notice that his latest gpdf is "bad". Distribution makers will 
also need a way to announce such things to their users. I have wondered if we 
could create a ipk with RCONFLICTS on discontinued software or such.


z.



      reply	other threads:[~2010-03-08  6:11 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
2010-03-08  6:08   ` Holger Hans Peter Freyther [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=201003080708.11546.holger+oe@freyther.de \
    --to=holger+oe@freyther.de \
    --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.