Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Urbanec <openembedded-devel@urbanec.net>
To: OE Core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Better support for upgrading packages in opkg and update-rc.d.bbclass
Date: Mon, 13 Oct 2014 16:23:12 +1100	[thread overview]
Message-ID: <543B61C0.6050500@urbanec.net> (raw)
In-Reply-To: <CANyK_8cZGNxd0=FKA1NK1Y69RaHT4bVry_FjixuQCMW1zPpsLA@mail.gmail.com>

On 12/10/14 06:17, Paul Barker wrote:
> opkg_remove_pkg is never called with from_upgrade set to a non-zero
> value. The removal of an old package during an upgrade is handled by
> directly calling remove_data_files_and_list and
> remove_maintainer_scripts from opkg_install_pkg. The desired behaviour
> is given in the comments in prerm_upgrade_old_pkg in opkg_install.c,
> the behaviour given by the comment in that function just needs
> implementing.

Indeed, I got fooled by looking at the call to opkg_install_pkg(pkg, 1)

> This is already entered as issue 104 in the opkg issue tracker:
> https://code.google.com/p/opkg/issues/detail?id=104

So it is. Slightly more work than my trivial opkg patch, but then again, 
my trivial opkg patch is not much use ;-) Please disregard it.

> Have you tested this patch before submitting it?

To be honest, I have not tested the opkg "upgrade" patch in isolation. I 
have tested the opkg patch for multiple package upgrade case together 
with my changes to update-rc.d.bbclass changes (i.e. the entire patch I 
posted to the oe-core list) and this has solved the problems that I 
encountered initially. The "fix" for my use case is due to the changes 
in the way the prerm, postrm and postinst scripts work, but reviewing 
those changes, that's not good enough either.

Thanks for the review.

I'll try again later...

Peter


  reply	other threads:[~2014-10-13  5:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 16:45 [PATCH] Better support for upgrading packages in opkg and update-rc.d.bbclass Peter Urbanec
2014-10-11 14:41 ` Paul Barker
2014-10-11 19:17   ` Paul Barker
2014-10-13  5:23     ` Peter Urbanec [this message]
2014-10-13 10:08       ` Paul Barker
2014-10-11 16:04 ` Andreas Oberritter
2014-10-16  1:51   ` Peter Urbanec
2014-10-16 20:55     ` Andreas Oberritter
2014-10-22 14:42       ` Peter Urbanec
2014-10-24 12:22         ` Andreas Oberritter

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=543B61C0.6050500@urbanec.net \
    --to=openembedded-devel@urbanec.net \
    --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