Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] libbonobo.inc: add libbonobo-bin package
Date: Tue, 18 Nov 2014 13:48:15 +0100	[thread overview]
Message-ID: <m4ff6f$nlo$1@ger.gmane.org> (raw)
In-Reply-To: <5464990A.5030400@windriver.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hongxu Jia schreef op 13-11-14 12:42:
> On 11/13/2014 07:02 PM, Koen Kooi wrote: Hongxu Jia schreef op 12-11-14
> 03:13:
>>>> The previous libbonobo package contains perl scripts, while
>>>> installing libbonobo, package management detected perl required,
>>>> but it actually not needed as lib. So add libbonobo-bin package to
>>>> contain these scripts. It refers debian:
>>>> https://packages.debian.org/sid/libbonobo2-bin
>>>> 
>>>> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> --- 
>>>> meta-gnome/recipes-gnome/bonobo/libbonobo.inc | 3 ++- 1 file
>>>> changed, 2 insertions(+), 1 deletion(-)
>>>> 
>>>> diff --git a/meta-gnome/recipes-gnome/bonobo/libbonobo.inc 
>>>> b/meta-gnome/recipes-gnome/bonobo/libbonobo.inc index
>>>> 8b6007e..e0f6168 100644 ---
>>>> a/meta-gnome/recipes-gnome/bonobo/libbonobo.inc +++ 
>>>> b/meta-gnome/recipes-gnome/bonobo/libbonobo.inc @@ -5,10 +5,11 @@ 
>>>> LIC_FILES_CHKSUM =
>>>> "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \ SECTION =
>>>> "x11/gnome/libs" DEPENDS = "glib-2.0 orbit2 intltool-native libxml2
>>>> dbus dbus-glib"
>>>> 
>>>> -inherit gnomebase gtk-doc +inherit gnomebase gtk-doc lib_package
>>>> 
>>>> ORBIT_IDL_SRC = "${STAGING_BINDIR_NATIVE}/orbit-idl-2"
>>>> 
>>>> +RDEPENDS_${PN}-bin = "${PN} perl" FILES_${PN} += 
>>>> "${libdir}/orbit-2.0/*.so ${libdir}/bonobo/monikers/*.so"
>>>> FILES_${PN}-dbg += "${libdir}/bonobo/monikers/.debug \ 
>>>> ${libdir}/bonobo-2.0/samples/.debug ${libdir}/orbit-2.0/.debug"
>>>> 
> This breaks the upgrade path
> 
>> I am sorry I do not understand what you mean, do you mean running
>> 'smart upgrade' failed?

You are moving files between packages, which makes 'opkg update ; opkg
upgrade' fail with conflicts unless you carefully craft RREPLACES/RCONFLICTS
or enforce ordering in upgrade order (which isn't currently possible).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFUa0APMkyGM64RGpERAh7AAJ9n0hIeX6jEo9x0C0H75SGUMShn2wCghoNe
sA1dMU2SBVy+tsLnEq+Qkks=
=2G5X
-----END PGP SIGNATURE-----



  reply	other threads:[~2014-11-18 12:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12  2:13 [PATCH V2 0/1] libbonobo.inc: add libbonobo-bin package Hongxu Jia
2014-11-12  2:13 ` [PATCH 1/1] " Hongxu Jia
2014-11-13 11:02   ` Koen Kooi
2014-11-13 11:42     ` Hongxu Jia
2014-11-18 12:48       ` Koen Kooi [this message]
2014-11-18 15:27         ` Paul Eggleton
2014-11-18 18:32           ` Koen Kooi
2014-11-19  0:36             ` Paul Eggleton
2014-11-19  7:53               ` Koen Kooi
2014-11-19 11:17                 ` Paul Eggleton
2014-11-19 14:10                   ` Koen Kooi
2014-11-13 15:22     ` Hongxu Jia
  -- strict thread matches above, loose matches on Subject: below --
2014-11-11 12:16 [PATCH 0/1] " Hongxu Jia
2014-11-11 12:16 ` [PATCH 1/1] " Hongxu Jia
2014-11-11 13:15   ` Paul Eggleton

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='m4ff6f$nlo$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox