From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Tarek El-Sherbiny <tarek.elsherbiny@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Smart PM for upgrade the full image
Date: Wed, 08 Jan 2014 15:39:04 +0000 [thread overview]
Message-ID: <2104439.ERPX2TAWut@helios> (raw)
In-Reply-To: <CAB3sqtaURWiPHOBHe4a5n3SGEskGrohRseT6S1X97K0SNcqZnw@mail.gmail.com>
On Wednesday 08 January 2014 14:07:57 Tarek El-Sherbiny wrote:
> On Wed, Jan 8, 2014 at 1:33 PM, Paul Eggleton <paul.eggleton@linux.intel.com
> > wrote:
> > On Wednesday 08 January 2014 12:52:42 Tarek El-Sherbiny wrote:
> > > I have several targets deployed in multiple sites. Each target might be
> > > running a different version of the product rootfs image. When I release
> > > a new rootfs image I would like to use the smart command on each target
> > > at the customer site to upgrade the software to the latest image. Going
> > > through each package and install it separately is inefficient way of
> > > handling the upgrade and I don't expect the customer to have the
> > > knowledge for doing so.
> > >
> > > What we really need is a smart command to compare the latest rootfs
> > > image and install, remove or un-change packages based on what is
> > > currently installed.
> > >
> > > Can the smart command achieve that or do I need to write my own script?
> >
> > Isn't this the same question you asked the other day? i.e., this is "smart
> > upgrade".
>
> Smart upgrade only upgrades packages that is currently installed. It
> doesn't install new packages nor remove unwanted packages.
> Is that not true?
That is true, yes. As far as I know, smart has no capabilities in this area
beyond what is offered through conflicts - and for situations where one package
replaces another, with any of the package management backends we support you
should use RPROVIDES + RREPLACES + RCONFLICTS to ensure that the old name is
redirected to the new name, new package is installed automatically, and the
old package is removed (respectively).
If it's a straight old image -> new image upgrade, you'll probably have to
look at other tools; package managers don't really handle this situation well
- at least not out of the box.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2014-01-08 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 12:52 Smart PM for upgrade the full image Tarek El-Sherbiny
2014-01-08 13:33 ` Paul Eggleton
2014-01-08 14:07 ` Tarek El-Sherbiny
2014-01-08 15:39 ` Paul Eggleton [this message]
2014-01-08 18:25 ` Tarek El-Sherbiny
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=2104439.ERPX2TAWut@helios \
--to=paul.eggleton@linux.intel.com \
--cc=tarek.elsherbiny@gmail.com \
--cc=yocto@yoctoproject.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.