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: Mon, 14 Feb 2011 15:27:23 +0000 [thread overview]
Message-ID: <1297697243.2178.97.camel@phil-desktop> (raw)
In-Reply-To: <20110214102232.GB8619@localhost.jama.net>
On Mon, 2011-02-14 at 11:22 +0100, Martin Jansa wrote:
> So can someone explain why we need that 'newpkg = pkg.replace(orig_pkg, devname, 1)' in else?
If that line was removed altogether then the -dev packages (and -doc,
-bin, ...) would stop being renamed, which wouldn't be a very good
thing. In other words, you'd get libncurses5 but ncurses-dev (not
libncurses5-dev) etc.
However you're right that the logic as it stands does look fairly
broken. Two ways of fixing it come to mind:
a) have it explicitly search for (and rename) [orig_pkg]-dev,
[orig_pkg]-doc etc, and remove the catch-all altogether; or
b) switch to a two-phase approach where it first renames all the
libraries themselves, then uses some heuristic to match the remaining
packages against the libraries and apply an appropriate renaming to
them. Probably just matching on longest substring would be good enough
here.
I think (b) is probably a better solution although it would be a little
harder to implement.
p.
next prev parent reply other threads:[~2011-02-14 15:27 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 [this message]
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
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=1297697243.2178.97.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.