From: Lianhao Lu <lianhao.lu@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Modified the vercmp() to meet Debian rules
Date: Thu, 12 Apr 2012 17:27:58 +0800 [thread overview]
Message-ID: <cover.1334222502.git.lianhao.lu@intel.com> (raw)
As we investigated, the vercmp() in bitbake didn't meet the Debian rules,
and is not compatible to what opkg expected. Detailed information could be
find at http://lists.linuxtogo.org/pipermail/bitbake-devel/2012-April/002641.html.
This patch fixed the vercmp() to meet the Debian rules.
The following changes since commit 4219e2ea033232d95117211947b751bdb5efafd4:
Saul Wold (1):
hig/builder: use the new which_terminal() function
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib llu/vercmp_bitbake
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=llu/vercmp_bitbake
Lianhao Lu (1):
bb.utils: Modifed vercmp() to meet Debian rules.
lib/bb/utils.py | 40 ++++++++++++++++------------------------
1 files changed, 16 insertions(+), 24 deletions(-)
next reply other threads:[~2012-04-12 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 9:27 Lianhao Lu [this message]
2012-04-12 9:28 ` [PATCH 1/1] bb.utils: Modifed vercmp() to meet Debian rules Lianhao Lu
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=cover.1334222502.git.lianhao.lu@intel.com \
--to=lianhao.lu@intel.com \
--cc=bitbake-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.