From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Kang Kai <kai.kang@windriver.com>
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] external-python-tarball: code refactoring
Date: Mon, 21 Jan 2013 10:25:40 +0000 [thread overview]
Message-ID: <1358763940.14265.45.camel@ted> (raw)
In-Reply-To: <36a8eaeb4853ea8ce5faa235e106e496b69bf356.1358754984.git.kai.kang@windriver.com>
On Mon, 2013-01-21 at 15:59 +0800, Kang Kai wrote:
> external-python-tarball only can be built when inherit package_ipk now.
> Update it and split the populate python operation to separated bbclass
> according the value of PACKAGE_CLASSES, then it could be built for rpm
> and deb too.
>
> [Yocto 3006]
>
> Signed-off-by: Kang Kai <kai.kang@windriver.com>
> ---
> meta/classes/populate_python_deb.bbclass | 42 ++++++++++++++
> meta/classes/populate_python_ipk.bbclass | 43 +++++++++++++++
> meta/classes/populate_python_rpm.bbclass | 59 ++++++++++++++++++++
> meta/recipes-core/meta/external-python-tarball.bb | 61 ++++-----------------
> 4 files changed, 155 insertions(+), 50 deletions(-)
> create mode 100644 meta/classes/populate_python_deb.bbclass
> create mode 100644 meta/classes/populate_python_ipk.bbclass
> create mode 100644 meta/classes/populate_python_rpm.bbclass
No, sorry but this isn't right. We already have package specific
functions to do these things, we should be trying to reuse those. If we
can't reuse the functions, we need to improve them so we can.
Cheers,
Richard
next prev parent reply other threads:[~2013-01-21 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 7:59 [PATCH 0/2] Refactor external-python-tarball Kang Kai
2013-01-21 7:59 ` [PATCH 1/2] createrepo-native: update dependency Kang Kai
2013-01-21 7:59 ` [PATCH 2/2] external-python-tarball: code refactoring Kang Kai
2013-01-21 10:25 ` Richard Purdie [this message]
2013-01-22 1:52 ` Kang Kai
-- strict thread matches above, loose matches on Subject: below --
2013-01-22 11:30 [PATCH 0/2] V2: Refactor external-python-tarball Kang Kai
2013-01-22 11:30 ` [PATCH 2/2] external-python-tarball: code refactoring Kang Kai
2013-01-22 16:58 ` Saul Wold
2013-01-23 2:35 ` Kang Kai
2013-01-23 3:13 [PATCH 0/2] V3: Refactor external-python-tarball.bb Kang Kai
2013-01-23 3:13 ` [PATCH 2/2] external-python-tarball: code refactoring Kang Kai
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=1358763940.14265.45.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=kai.kang@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