From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/3] libcec: update libcec to latest version (1.8.2) as to include RasPi support
Date: Thu, 06 Sep 2012 09:47:59 +0100 [thread overview]
Message-ID: <5048633F.4080405@communistcode.co.uk> (raw)
In-Reply-To: <CAK18fxG+1gL2q4DL=3=wBQhyga70fONp-7uNhPiutqAUTMCMXg@mail.gmail.com>
On 06/09/12 09:37, Andrei Gherzan wrote:
> On Thu, Sep 6, 2012 at 11:12 AM, Jack Mitchell <ml@communistcode.co.uk>wrote:
>
>> On 05/09/12 22:32, Paul Eggleton wrote:
>>
>>> On Wednesday 05 September 2012 21:28:18 Martin Jansa wrote:
>>>
>>>> On Wed, Sep 05, 2012 at 03:16:10PM +0100, Paul Eggleton wrote:
>>>>
>>>>> It's not totally clear but it doesn't look like 1.8.2 has been released
>>>>> yet judging from their website; if that's the case then PV should be set
>>>>> to "1.8.1+git${SRCPV}".
>>>>>
>>>> Or rather
>>>> "1.8.1+gitr${SRCPV}"
>>>> like most meta-* recipes
>>>>
>>> This was discussed not that long ago IIRC - the r is superfluous for git.
>>> In
>>> fact if you look at most OE-Core recipes that use SRCPV they do not
>>> precede it
>>> with r.
>>>
>>> Cheers,
>>> Paul
>>>
>>>
>> So even though it is the 1.8.1 release commit it should still be tagged
>> with the git SRCPV?
>>
>>
> No. The SRCPV should be there to indicate that your version is something in
> between 2 official versions. In your case as there is not
> 1.8.2 officially you state that this package is 1.8.1 but at a
> later SRCPV commit.
>
> You need v1.8.2? There is no rpi support in 1.8.1? Why don't you update to
> that version?
>
> Andrei
There is RPi support merged in 1.8.1 - I had read the changelog to get
the version number and they had listed 1.8.2 in it which lead me to
believe it was already at 1.8.2 but it was just a 'work in progress' 1.8.2.
The current commit is the 1.8.1 tag and has the features I need so I
don't need to put in a 1.8.1+wip.
Regards,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
prev parent reply other threads:[~2012-09-06 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 14:02 [PATCH 1/3] libplist: issues with parallel make so disable ml
2012-09-05 14:02 ` [PATCH 2/3] liblockdev: new recipe, new version of libcec requires it ml
2012-09-05 14:02 ` [PATCH 3/3] libcec: update libcec to latest version (1.8.2) as to include RasPi support ml
2012-09-05 14:16 ` Paul Eggleton
2012-09-05 19:28 ` Martin Jansa
2012-09-05 21:32 ` Paul Eggleton
2012-09-06 8:12 ` Jack Mitchell
2012-09-06 8:30 ` Paul Eggleton
2012-09-06 8:48 ` Jack Mitchell
2012-09-06 8:37 ` Andrei Gherzan
2012-09-06 8:47 ` Jack Mitchell [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=5048633F.4080405@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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.