From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [oe-commits] Martin Jansa : xserver-xorg: use EXTENDPKGV instead of PV in RCONFLICTS_${PN}-module-exa
Date: Thu, 27 Sep 2012 17:41:03 -0500 [thread overview]
Message-ID: <5064D5FF.2050409@windriver.com> (raw)
In-Reply-To: <CAP9ODKr0nC2WbN=gCieWRnf4=-9SiiB6NUiubVrTxnnvbAaGtg@mail.gmail.com>
Just an FYI -- Martin Jansa found a problem with the implement of the package
version comparison.
In deb and ipk, they do not support '<' or '>', instead it's '<<' and '>>'.
(Odd, historical reasons apparently).
While RPM doesn't have any idea what '<<' or '>>' is.
Talking with RP and others it seems like the best approach is to implement a
conversion, in the deb and ipk packaging classes, to convert '<' and '>' to the
'<<' and '>>' equivalents. As well as add a sanity check that nobody is using
'<<' or '>>'.
I'm in the process of doing that now.
--Mark
On 9/27/12 1:08 PM, Otavio Salvador wrote:
> On Thu, Sep 27, 2012 at 2:55 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> On Thu, Sep 27, 2012 at 05:34:19PM +0200, Martin Jansa wrote:
>>> On Thu, Sep 27, 2012 at 02:29:25PM +0000, git@git.openembedded.org wrote:
>>>> Module: openembedded-core.git
>>>> Branch: master
>>>> Commit: ed0216d29fc4355c5220f3ad51df04a63cacb0c3
>>>> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=ed0216d29fc4355c5220f3ad51df04a63cacb0c3
>>>>
>>>> Author: Martin Jansa <martin.jansa@gmail.com>
>>>> Date: Sat Sep 22 19:13:14 2012 +0200
>>>>
>>>> xserver-xorg: use EXTENDPKGV instead of PV in RCONFLICTS_${PN}-module-exa
>>>>
>>>> * it doesn't make much sense with PV, because xserver-xorg-module-exa
>>>> was introduced in
>>>> http://git.openembedded.org/openembedded-core/commit/meta/recipes-graphics/xorg-xserver?id=1a666ee1cda3c0b74daba5881fc5f62e13deec66
>>>> so our xserver-xorg-module-exa RCONFLICTS with xserver-xorg (<= 1.11.2-r4)
>>>> and (< 1.11.2) is not good enough
>>>>
>>>> * because we don't know how many PRINC are in BSP/DISTRO layers,
>>>> then it's safer to RCONFLICTS with every older version then current
>>>> EXTENDPKGV
>>>>
>>>> Also fixes whitespace to work correctly with opkg
>>>
>>> The whitespace problem wasn't opkg fault AFAIK, but
>>> bb.utils.explode_dep_versions as shown in
>>> http://patchwork.openembedded.org/patch/37069/
>>
>> Ah and it was meant to be applied together with this patch, so now it's
>> missing PR bump..
>
> It keeps failing for me.
>
next prev parent reply other threads:[~2012-09-27 22:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120927142926.CA9C5103AC@opal>
2012-09-27 15:34 ` [oe-commits] Martin Jansa : xserver-xorg: use EXTENDPKGV instead of PV in RCONFLICTS_${PN}-module-exa Martin Jansa
2012-09-27 17:55 ` Martin Jansa
2012-09-27 18:08 ` Otavio Salvador
2012-09-27 22:41 ` Mark Hatle [this message]
2012-09-27 22:50 ` Martin Jansa
2012-09-28 12:02 ` Otavio Salvador
2012-09-29 8:43 ` Martin Jansa
2012-09-29 17:09 ` [PATCH] opkg: fix version constraints in conflicts, depends, replaces Martin Jansa
2012-09-29 17:19 ` [PATCHv2] " Martin Jansa
2012-09-30 9:06 ` Martin Jansa
2012-09-30 12:53 ` Martin Jansa
2012-10-01 11:41 ` [PATCHv3] " Martin Jansa
2012-10-02 15:12 ` Saul Wold
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=5064D5FF.2050409@windriver.com \
--to=mark.hatle@windriver.com \
--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