From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/9] package_rpm.bbclass: create method for createrepo cmd
Date: Mon, 23 May 2011 15:39:07 +0100 [thread overview]
Message-ID: <1306161547.3424.853.camel@rex> (raw)
In-Reply-To: <ba11e66609ecaad27a4c225ee1e21d60a330d8f9.1306089781.git.sgw@linux.intel.com>
A couple of comments:
Firstly the commit message says what you changed, not why...
On Sun, 2011-05-22 at 11:48 -0700, Saul Wold wrote:
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> meta/classes/package_rpm.bbclass | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/package_rpm.bbclass b/meta/classes/package_rpm.bbclass
> index 1d8c686..666eb54 100644
> --- a/meta/classes/package_rpm.bbclass
> +++ b/meta/classes/package_rpm.bbclass
> @@ -15,6 +15,10 @@ python package_rpm_install () {
> bb.fatal("package_rpm_install not implemented!")
> }
>
> +package_createrepo () {
> + createrepo ${DEPLOY_DIR_RPM}
> +}
> +
> RPMCONF_TARGET_BASE = "${DEPLOY_DIR_RPM}/solvedb"
> RPMCONF_HOST_BASE = "${DEPLOY_DIR_RPM}/solvedb-sdk"
> #
> @@ -816,6 +820,6 @@ python do_package_write_rpm () {
> do_package_write_rpm[dirs] = "${PKGWRITEDIRRPM}"
> addtask package_write_rpm before do_package_write after do_package
>
> -PACKAGEINDEXES += "package_update_index_rpm; createrepo ${DEPLOY_DIR_RPM};"
> +PACKAGEINDEXES += "package_update_index_rpm; package_createrepo"
Secondly this should end in a ;. I'd just add the
package_update_index_rpm call to package_createrepo to be honest.
package_createrepo could also do with rpm in the name somewhere just to
we're reminded its rpm specific in other contexts.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-23 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 18:48 [PATCH 0/9] UPDATED: 21/22-May 2011 Pull Saul Wold
2011-05-22 18:48 ` [PATCH 1/9] gail: Add LIC_FILES_CHKSUM Saul Wold
2011-05-23 9:31 ` Phil Blundell
2011-05-22 18:48 ` [PATCH 2/9] update-alternatives-dpkg: Update to dpkg base 1.15.8.7 Saul Wold
2011-05-22 21:20 ` Joshua Lock
2011-05-23 9:29 ` Phil Blundell
2011-05-22 18:48 ` [PATCH 3/9] puzzles: update to r9173 Saul Wold
2011-05-22 18:48 ` [PATCH 4/9] package_rpm.bbclass: create method for createrepo cmd Saul Wold
2011-05-22 21:21 ` Joshua Lock
2011-05-23 14:39 ` Richard Purdie [this message]
2011-05-22 18:48 ` [PATCH 5/9] distcc_2.18.3.bb: Fix compilation on uclibc Saul Wold
2011-05-22 18:48 ` [PATCH 6/9] opkg_svn.bb: Install rcS.d into $D instead of $IMAGE_ROOTFS Saul Wold
2011-05-22 18:48 ` [PATCH 7/9] tcmode-default: switch to eglibc 2.13 from 2.12 Saul Wold
2011-05-22 18:48 ` [PATCH 8/9] tcmode-default: switch to gcc 4.6.0 for ppc & mips also Saul Wold
2011-05-22 18:48 ` [PATCH 9/9] gplv2 recipes update upstream status of patches Saul Wold
2011-05-23 14:36 ` [PATCH 0/9] UPDATED: 21/22-May 2011 Pull Richard Purdie
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=1306161547.3424.853.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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