From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libfribidi-0.10.4: update recipe, fix packaging
Date: Mon, 18 Oct 2010 12:21:50 +0200 [thread overview]
Message-ID: <4CBC1FBE.9020808@opendreambox.org> (raw)
In-Reply-To: <i9gsjn$8r0$3@dough.gmane.org>
On 10/18/2010 09:22 AM, Koen Kooi wrote:
> On 18-10-10 00:15, Andreas Oberritter wrote:
>> * added LICENSE
>> * removed configure patch
>> * use lib_package and binconfig to package all installed files
>
> What's the upgrade path? I assume package names have changes due to this.
I guess my patch description wasn't clear enough.
The previously unpackaged files ${bindir}/fribidi and
${bindir}/fribidi-config are now packaged into libfribidi-bin and
libfribidi-dev, respectively.
The only file which moved to a different package is libfribidi.a, from
libfribidi-static to libfribidi-dev.
Does this change require special treatment for upgrades?
Regards,
Andreas
next prev parent reply other threads:[~2010-10-18 10:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 22:15 [PATCH] libfribidi-0.10.4: update recipe, fix packaging Andreas Oberritter
2010-10-18 7:22 ` Koen Kooi
2010-10-18 10:21 ` Andreas Oberritter [this message]
2010-10-18 10:48 ` Koen Kooi
2010-10-18 11:41 ` Andreas Oberritter
2010-10-19 18:01 ` [RFC] update lib_package.bbclass Andreas Oberritter
2010-10-20 7:47 ` Koen Kooi
2010-10-20 10:50 ` Andreas Oberritter
2010-10-25 14:20 ` [PATCH] lib_package.bbclass: fix packaging of static libs, inherit binconfig Andreas Oberritter
2010-11-13 16:28 ` Andreas Oberritter
2010-11-13 19:12 ` Tom Rini
2010-11-14 23:49 ` Andreas Oberritter
2010-11-15 15:07 ` Tom Rini
2010-11-15 15:46 ` Andreas Oberritter
2010-11-15 18:11 ` Tom Rini
2010-11-16 11:52 ` Andreas Oberritter
2010-11-16 16:51 ` [PATCH] libfribidi-0.10.4: update recipe, fix packaging 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=4CBC1FBE.9020808@opendreambox.org \
--to=obi@opendreambox.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.