From: Andrei Gherzan <andrei@gherzan.ro>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Package Updates
Date: Mon, 28 May 2012 14:21:30 +0300 [thread overview]
Message-ID: <4FC35FBA.2060200@gherzan.ro> (raw)
In-Reply-To: <4FC35FAD.7090505@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
On 05/28/2012 02:21 PM, Radu Moisan wrote:
>
>
> On 05/28/2012 01:55 PM, Burton, Ross wrote:
>> Hi,
>>
>> First, sorry for the thread breaking, I've just joined this list and I
>> didn't get this mail.
>>
>> Koen Kooi wrote:
>>>> dbus: Update to version 1.5.12
>>> First: how was this tested?
> the only testing I've done so far is to ensure it build and then check
> the version with dbus-daemon --version
Dbus comes with a test suite. Running those should be a must.
>>> Second: From the dbus website:
>>>
>>> The current stable branch is D-Bus 1.4.x. This is the recommended
>>> version for most purposes.
>>> The current development branch is D-Bus 1.5.x, which will lead to a
>>> 1.6.x stable branch in future.
>>>
>>> Why are you deleting the stable branch based recipe and add one from
>>> the development branch?
>> The definition of stable and unstable in DBus isn't as hard and fast
>> as you'd really like -- the 1.5.x cycle is very slow and mostly stable
>> from a crashy point of view.
>>
>> I'd say there is a good rationale for having both 1.4.x (.20, so that
>> also needs an upgrade) and 1.5.x in oe-core. The default should be
>> 1.4 for obvious reasons (it's the stable release), and 1.5 should be
>> there for people who need the improvements. In particular there has
>> been a lot of work on performance, so anyone heavily using dbus (i.e.
>> anything using Telepathy, which is where the improvements came from)
>> should look at 1.5 because it will give a noticeable improvement on
>> slower hardware.
>>
>> Ross
> I suppose, then, I should add another recipe and support both.
> However, can someone point out how can I make one of them default.
DEFAULT_PREFERENCE
@g
[-- Attachment #2: Type: text/html, Size: 2889 bytes --]
next prev parent reply other threads:[~2012-05-28 11:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 10:55 [PATCH 0/3] Package Updates Burton, Ross
2012-05-28 11:21 ` Radu Moisan
2012-05-28 11:21 ` Andrei Gherzan [this message]
2012-05-28 12:07 ` Paul Eggleton
2012-05-28 13:24 ` Radu Moisan
2012-05-28 13:26 ` Andrei Gherzan
2012-05-28 13:30 ` Burton, Ross
2012-05-28 13:44 ` Richard Purdie
2012-05-28 13:47 ` Burton, Ross
2012-05-28 13:58 ` Andrei Gherzan
2012-05-29 12:10 ` Philip Balister
2012-05-29 14:04 ` Radu Moisan
2012-05-29 8:29 ` dbus test suite Radu Moisan
2012-05-29 9:23 ` Radu Moisan
2012-05-29 9:28 ` Andrei Gherzan
2012-05-29 9:41 ` Radu Moisan
2012-05-29 9:42 ` Florin Sarbu
2012-05-29 11:18 ` Radu Moisan
2012-05-29 6:28 ` [PATCH 0/3] Package Updates Radu Moisan
2012-05-29 6:58 ` Radu Moisan
-- strict thread matches above, loose matches on Subject: below --
2014-03-10 3:48 Saul Wold
2013-12-10 19:16 Saul Wold
2013-08-05 21:07 Saul Wold
2013-07-23 23:53 Saul Wold
2012-05-29 7:01 Sarbu, Florin-Ionut (Florin)
2012-05-29 7:25 ` Radu Moisan
2012-05-25 8:50 Radu Moisan
2012-05-25 9:52 ` Koen Kooi
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=4FC35FBA.2060200@gherzan.ro \
--to=andrei@gherzan.ro \
--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