Openembedded Core Discussions
 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>
Subject: Re: [PATCH] rootfs_ipk: implement FEED_DEPLOYDIR_BASE_URI support
Date: Thu, 08 Dec 2011 10:10:14 -0800	[thread overview]
Message-ID: <4EE0FD86.2030908@linux.intel.com> (raw)
In-Reply-To: <1323202770-19265-1-git-send-email-eric@eukrea.com>

On 12/06/2011 12:19 PM, Eric Bénard wrote:
> this feature was present in OE-classic, is documented in OE-core
> but its implementation is actually missing.
> The present implementation is directly copied from OE-classic
> and tested on an arm926 machine.
>
> Signed-off-by: Eric Bénard<eric@eukrea.com>
> ---
>   meta/classes/rootfs_ipk.bbclass |   13 ++++++++++++-
>   1 files changed, 12 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/rootfs_ipk.bbclass b/meta/classes/rootfs_ipk.bbclass
> index b4b95c5..ec01951 100644
> --- a/meta/classes/rootfs_ipk.bbclass
> +++ b/meta/classes/rootfs_ipk.bbclass
> @@ -205,7 +205,18 @@ ipk_insert_feed_uris () {
>
>   		# insert new feed-sources
>   		echo "src/gz $feed_name $feed_uri">>  ${IPKGCONF_TARGET}
> -        done
> +	done
> +
> +	# Allow to use package deploy directory contents as quick devel-testing
> +	# feed. This creates individual feed configs for each arch subdir of those
> +	# specified as compatible for the current machine.
> +	# NOTE: Development-helper feature, NOT a full-fledged feed.
> +	if [ -n "${FEED_DEPLOYDIR_BASE_URI}" ]; then
> +		for arch in ${PACKAGE_ARCHS}
> +		do
> +			echo "src/gz local-$arch ${FEED_DEPLOYDIR_BASE_URI}/$arch">>  ${IMAGE_ROOTFS}/etc/opkg/local-$arch-feed.conf
> +	    done
> +	fi
>   }
>
>   python () {

Merged into OE-Core

Thanks
	Sau!




      reply	other threads:[~2011-12-08 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 20:19 [PATCH] rootfs_ipk: implement FEED_DEPLOYDIR_BASE_URI support Eric Bénard
2011-12-08 18:10 ` 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=4EE0FD86.2030908@linux.intel.com \
    --to=sgw@linux.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