From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Problem with debian renaming and upgrade-path on dora
Date: Fri, 1 Aug 2014 12:52:03 +0200 [thread overview]
Message-ID: <20140801105203.GC16445@jama> (raw)
In-Reply-To: <1635829.5tfOCJn7de@peggleto-mobl5.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
On Fri, Aug 01, 2014 at 10:32:38AM +0100, Paul Eggleton wrote:
> Hi Henning,
>
> On Tuesday 29 July 2014 19:32:51 Henning Heinold wrote:
> > I have a problem to get a sane upgrade path for a library package which
> > should be splitted in to serval packages on dora.
> >
> > The old package is called libfoo now the package gets split into libfoo
> > libfoo-bar libfoo-set and so on.
> >
> > Because of the debian renaming for libraries the PN-library package libfoo
> > is renamed to libfoo3.
> >
> > If we now want to upgrade from libfoo to libfoo3 oneway would be to use
> > RREPLACE, but the renaming wrapping is written at do_package into files,
> > before all the other stuff kicks in.
> >
> > So all RREPLACES are renamed to libfoo3 too, making it impossible to get a
> > REPLACE stanza for libfoo into an ipk.
Why do you want to do the upgrade one-way?
I think that one of debian renaming benefits is that the old libfoo
package stays installed on target until all programs aren't rebuilt
against libfoo3 and upgraded - then old libfoo could be automatically
uninstalled as orphaned package.
> Hmm. I guess one workaround for this would be to set the RREPLACES / RPROVIDES
> / RCONFLICTS in a Python function that is called after the debian renaming
> happens.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2014-08-01 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 17:32 Problem with debian renaming and upgrade-path on dora Henning Heinold
2014-08-01 9:32 ` Paul Eggleton
2014-08-01 10:52 ` Martin Jansa [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=20140801105203.GC16445@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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