All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] rootfs_ipk.bbclass: fix BAD_RECOMMENDATIONS
Date: Wed, 24 Feb 2010 18:06:29 -0500	[thread overview]
Message-ID: <20100224230629.GA8672@denix.org> (raw)
In-Reply-To: <1267048766.5437.330.camel@lenovo.internal.reciva.com>

On Wed, Feb 24, 2010 at 09:59:26PM +0000, Phil Blundell wrote:
> On Thu, 2010-02-25 at 08:18 +1030, Graham Gower wrote:
> > This is an unintended side effect of other changes, however I'm not
> > sure that I consider it inappropriate behaviour. That status does
> > apply to a particular package version, does it not?
> 
> No, the SW_xx flags should apply to any version and architecture rather
> than being nailed down to a specific tuple.  Otherwise, these flags
> would be subverted as soon as a new version appears in the feed.

The thing is, those SW_xx flags are not preserved anyway - the status file is 
primed with BAD_RECOMMENDATIONS (Status: deinstall), but later gets 
overwritten by the list of only installed packages. Of course, "deinstall" 
packages are being skipped, but they are not preserved in the status file for 
later use...

But, on the other hand, if there are multiple versions of the package present 
in the deploy/feed, then it will, probably, deinstall one version and install 
another one, which is not the correct behavior.

-- 
Denys



  reply	other threads:[~2010-02-24 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 20:52 [PATCH] rootfs_ipk.bbclass: fix BAD_RECOMMENDATIONS Denys Dmytriyenko
2010-02-24 21:00 ` Phil Blundell
2010-02-24 21:48   ` Graham Gower
2010-02-24 21:59     ` Phil Blundell
2010-02-24 23:06       ` Denys Dmytriyenko [this message]
2010-02-24 23:15         ` Phil Blundell
  -- strict thread matches above, loose matches on Subject: below --
2010-08-18  5:51 [PATCH] rootfs_ipk.bbclass: Fix BAD_RECOMMENDATIONS Graham Gower
2010-08-19  5:32 ` Martin Jansa

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=20100224230629.GA8672@denix.org \
    --to=denis@denix.org \
    --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.