All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH v2] opkg-nogpg: add file path
Date: Fri, 25 May 2012 09:41:58 -0700	[thread overview]
Message-ID: <4FBFB656.7030102@linux.intel.com> (raw)
In-Reply-To: <1337875572-17969-1-git-send-email-paul.eggleton@linux.intel.com>

On 05/24/2012 09:06 AM, Paul Eggleton wrote:
> There was no explicit path in FILESPATH for this recipe to allow it to
> find files referred to in SRC_URI (files shared with the standard opkg
> recipe). This problem may have been masked by the fetcher behaviour of
> looking for files last in DL_DIR, thus if opkg has been fetched
> beforehand there would have been no error.
>
> Signed-off-by: Paul Eggleton<paul.eggleton@linux.intel.com>
> ---
>   meta/recipes-devtools/opkg/opkg-nogpg_0.1.8.bb |    2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-devtools/opkg/opkg-nogpg_0.1.8.bb b/meta/recipes-devtools/opkg/opkg-nogpg_0.1.8.bb
> index 259a60e..da2a39c 100644
> --- a/meta/recipes-devtools/opkg/opkg-nogpg_0.1.8.bb
> +++ b/meta/recipes-devtools/opkg/opkg-nogpg_0.1.8.bb
> @@ -3,6 +3,8 @@ require opkg_${PV}.bb
>   DEPENDS = "curl"
>   PROVIDES += "opkg"
>
> +FILESEXTRAPATHS_prepend := "${THISDIR}/opkg-${PV}:"
> +
>   EXTRA_OECONF += "--disable-gpg"
>
>   DEFAULT_PREFERENCE = "-1"

Merged into OE-Core

Thanks
	Sau!



      reply	other threads:[~2012-05-25 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 16:06 [PATCH v2] opkg-nogpg: add file path Paul Eggleton
2012-05-25 16:41 ` Saul Wold [this message]

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=4FBFB656.7030102@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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.