From: Martin Jansa <martin.jansa@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-commits] Martin Jansa : xserver-xorg: use EXTENDPKGV instead of PV in RCONFLICTS_${PN}-module-exa
Date: Sat, 29 Sep 2012 10:43:17 +0200 [thread overview]
Message-ID: <20120929084317.GH3049@jama.jama.net> (raw)
In-Reply-To: <CAP9ODKpKzc2T7MpMckyTabvuAkAe1ABCyZLKSz0=z83gJjAh1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]
On Fri, Sep 28, 2012 at 09:02:47AM -0300, Otavio Salvador wrote:
> On Thu, Sep 27, 2012 at 7:50 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Fri, Sep 28, 2012 at 12:41 AM, Mark Hatle <mark.hatle@windriver.com> wrote:
> >> 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
> >
> > There is still some problem in opkg, now when I'm testing << with opkg
> > which should work as LESS (and < as LESS_EQUAL), it still shows <= in
> > opkg status and behaves like <=. So there is probably some bug in opkg
> > still hidden :/
>
> Yes; it seems the right fix is in opkg.
>
> Using RCONFLICTS with << also fails to me as said yestarday on IRC.
Reported upstream with simple test case
http://code.google.com/p/opkg/issues/detail?id=94
will attach patch there + send here when I have it.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-09-29 8:55 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
2012-09-27 22:50 ` Martin Jansa
2012-09-28 12:02 ` Otavio Salvador
2012-09-29 8:43 ` Martin Jansa [this message]
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=20120929084317.GH3049@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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