From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] opkg_svn.bb: Install rcS.d into ${D} instead of ${IMAGE_ROOTFS}
Date: Fri, 20 May 2011 16:30:19 -0700 [thread overview]
Message-ID: <4DD6F98B.7090700@intel.com> (raw)
In-Reply-To: <43cfb965113150ea56c55c3880b67ba272b3c719.1305933509.git.raj.khem@gmail.com>
On 05/20/2011 04:19 PM, Khem Raj wrote:
> Remove headerfix.patch, its already applied upstream
>
Minor nit, should be $D in the subject line also right?
Sau!
> Signed-off-by: Khem Raj<raj.khem@gmail.com>
> ---
> meta/recipes-devtools/opkg/opkg/headerfix.patch | 19 -------------------
> meta/recipes-devtools/opkg/opkg_svn.bb | 3 +--
> 2 files changed, 1 insertions(+), 21 deletions(-)
> delete mode 100644 meta/recipes-devtools/opkg/opkg/headerfix.patch
>
> diff --git a/meta/recipes-devtools/opkg/opkg/headerfix.patch b/meta/recipes-devtools/opkg/opkg/headerfix.patch
> deleted file mode 100644
> index b3515a0..0000000
> --- a/meta/recipes-devtools/opkg/opkg/headerfix.patch
> +++ /dev/null
> @@ -1,19 +0,0 @@
> -Without this, the FILE reference in this header can cause compile issues.
> -
> -RP - 29/1/10
> -
> -Upstream-Status: Pending
> -
> -Index: trunk/libopkg/pkg_dest.h
> -===================================================================
> ---- trunk.orig/libopkg/pkg_dest.h 2010-01-29 09:37:22.000000000 +0000
> -+++ trunk/libopkg/pkg_dest.h 2010-01-29 09:37:33.000000000 +0000
> -@@ -18,6 +18,8 @@
> - #ifndef PKG_DEST_H
> - #define PKG_DEST_H
> -
> -+#include<stdio.h>
> -+
> - typedef struct pkg_dest pkg_dest_t;
> - struct pkg_dest
> - {
> diff --git a/meta/recipes-devtools/opkg/opkg_svn.bb b/meta/recipes-devtools/opkg/opkg_svn.bb
> index 5964a47..3f2c22b 100644
> --- a/meta/recipes-devtools/opkg/opkg_svn.bb
> +++ b/meta/recipes-devtools/opkg/opkg_svn.bb
> @@ -11,7 +11,6 @@ RREPLACES_${PN} = "opkg-nogpg"
>
> SRC_URI = "svn://opkg.googlecode.com/svn;module=trunk;proto=http \
> file://add_vercmp.patch \
> - file://headerfix.patch \
> "
>
> S = "${WORKDIR}/trunk"
> @@ -34,7 +33,7 @@ do_install_append() {
> pkg_postinst_${PN} () {
> #!/bin/sh
> if [ "x$D" != "x" ]; then
> - install -d ${IMAGE_ROOTFS}/${sysconfdir}/rcS.d
> + install -d $D/${sysconfdir}/rcS.d
> # this happens at S98 where our good 'ole packages script used to run
> echo "#!/bin/sh
> opkg-cl configure
next prev parent reply other threads:[~2011-05-20 23:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 23:19 [PATCH 0/2] Opkg and distcc fix Khem Raj
2011-05-20 23:19 ` [PATCH 1/2] opkg_svn.bb: Install rcS.d into ${D} instead of ${IMAGE_ROOTFS} Khem Raj
2011-05-20 23:30 ` Saul Wold [this message]
2011-05-21 0:41 ` Khem Raj
2011-05-21 8:00 ` Phil Blundell
2011-05-21 23:04 ` Khem Raj
2011-05-20 23:19 ` [PATCH 2/2] distcc_2.18.3.bb: Fix compilation on uclibc Khem Raj
2011-05-20 23:31 ` Richard Purdie
2011-05-21 0:43 ` Khem Raj
2011-05-21 0:48 ` Khem Raj
2011-05-21 6:23 ` Koen Kooi
2011-05-21 6:34 ` Phil Blundell
2011-05-21 7:19 ` Khem Raj
2011-05-21 7:45 ` Phil Blundell
2011-05-21 19:17 ` Koen Kooi
2011-05-21 23:03 ` Khem Raj
2011-05-23 19:09 ` [PATCH 0/2] Opkg and distcc fix Saul Wold
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=4DD6F98B.7090700@intel.com \
--to=saul.wold@intel.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