From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: debian.bbclass issues when some package is substring of another
Date: Thu, 17 Feb 2011 16:33:19 +0000 [thread overview]
Message-ID: <1297960399.2178.216.camel@phil-desktop> (raw)
In-Reply-To: <20110215103626.GF8619@localhost.jama.net>
On Tue, 2011-02-15 at 11:36 +0100, Martin Jansa wrote:
> Ah sorry, I didn't read your (b) properly, now I see last sentence about
> "longest substring".
>
> But that's mostly what reverse sorted patch does now, isn't it? Longer
> patterns are replaced before their shorter substrings (which then
> matches only to their proper packages, because longer were already
> replaced while handling longer pattern and "normally" doesn't match
> anymore).
Yeah, I think that's probably true. I haven't managed to convince
myself entirely that the reverse sorting patch is safe in all
situations, but neither have I been able to think of a case that my
algorithm would get right and yours would get wrong. So I think you
might as well go ahead and check in your patch, and we can revisit it in
the future if further problems do pop up.
p.
prev parent reply other threads:[~2011-02-17 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 10:22 debian.bbclass issues when some package is substring of another Martin Jansa
2011-02-14 11:45 ` Martin Jansa
2011-02-14 15:27 ` Phil Blundell
2011-02-15 9:15 ` Martin Jansa
2011-02-15 9:42 ` [PATCH] debian.bbclass: call auto_libname in reverse sorted AUTO_LIBNAME_PKGS Martin Jansa
2011-02-15 10:06 ` debian.bbclass issues when some package is substring of another Martin Jansa
2011-02-15 10:19 ` Phil Blundell
2011-02-15 10:36 ` Martin Jansa
2011-02-17 16:33 ` Phil Blundell [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=1297960399.2178.216.camel@phil-desktop \
--to=philb@gnu.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.