From: Saul Wold <sgw@linux.intel.com>
To: Trevor Woerner <trevor.woerner@linaro.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] runtime package management: ipk/opk
Date: Fri, 01 Nov 2013 12:35:23 -0700 [thread overview]
Message-ID: <5274027B.5060106@linux.intel.com> (raw)
In-Reply-To: <1383237932-13177-1-git-send-email-trevor.woerner@linaro.org>
On 10/31/2013 09:45 AM, Trevor Woerner wrote:
> Place the on-target feed configuration into the "base-feeds.conf" file instead
> of the "opkg.conf" file.
>
This says what you are doing, but the question is why is the change
needed? It might be obvious to you, but not to others. The
base-feeds.conf file is provided via the a distro configuration, so it's
not guarenteed to be there for every distro, so I am not sure this
change is correct.
Also for future referece the commit message should follow the commit
guidelines:
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Thanks
Sau!
> Signed-off-by: Trevor Woerner <trevor.woerner@linaro.org>
> ---
> meta/classes/rootfs_ipk.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/rootfs_ipk.bbclass b/meta/classes/rootfs_ipk.bbclass
> index b0805dc..1537af4 100644
> --- a/meta/classes/rootfs_ipk.bbclass
> +++ b/meta/classes/rootfs_ipk.bbclass
> @@ -159,7 +159,7 @@ ipk_insert_feed_uris () {
> echo "Added $feed_name feed with URL $feed_uri"
>
> # insert new feed-sources
> - echo "src/gz $feed_name $feed_uri" >> ${IPKGCONF_TARGET}
> + echo "src/gz $feed_name $feed_uri" >> ${IMAGE_ROOTFS}/${sysconfdir}/opkg/base-feeds.conf
> done
>
> # Allow to use package deploy directory contents as quick devel-testing
>
next prev parent reply other threads:[~2013-11-01 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 16:45 [PATCH] runtime package management: ipk/opk Trevor Woerner
2013-11-01 19:35 ` Saul Wold [this message]
2013-11-02 17:38 ` Trevor Woerner
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=5274027B.5060106@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=trevor.woerner@linaro.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