All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org, Scott Rifenbark <srifenbark@gmail.com>,
	Ayoub Zaki <ayoub.zaki@googlemail.com>
Subject: Re: FEED_DEPLOYDIR_BASE_URI does not work
Date: Tue, 1 Dec 2015 12:38:01 -0600	[thread overview]
Message-ID: <565DE909.80007@linux.intel.com> (raw)
In-Reply-To: <2445935.qXt4qp3rbC@peggleto-mobl.ger.corp.intel.com>



On 12/01/2015 12:16 PM, Paul Eggleton wrote:
> On Tue, 01 Dec 2015 08:34:15 Leonardo Sandoval wrote:
>> On 12/01/2015 03:49 AM, Ayoub Zaki wrote:
>>> |Hello,
>>>
>>> Setting FEED_DEPLOYDIR_BASE_URI
>>> <http://www.yoctoproject.org/docs/2.0/mega-manual/mega-manual.html#var-FEE
>>> D_DEPLOYDIR_BASE_URI> in local.conf as specified in the yocto manual does
>>> NOT generate any /etc/opkg/base-feeds.conf in the root of the target
>>> filesystem!
>>> Is ist a known bug ? I'm using jethro version with opkg as package
>>> manager.
>> Looks like a bug, so file a bug on bugzilla.yoctoproject.org.
>>
>> Have you tried setting the variables named
>> PACKAGE_FEED_[URIS|BASE_PATHS|ARCHS] ?
>>
>> http://www.yoctoproject.org/docs/2.0/mega-manual/mega-manual.html#var-PACKAG
>> E_FEED_URIS
> Leo - I'm not sure your patch implementing this functionality actually got
> merged in the end, though I suspect the corresponding changes to the manual
> did in advance (if that's the case, that shouldn't have happened). Can you
> double-check this?
Paul, you are right, patch is not yet on master but documentation is 
already there. I will reply the original email so it is taken into 
account for the next merge.

>
> Thanks,
> Paul
>



      reply	other threads:[~2015-12-01 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01  9:49 FEED_DEPLOYDIR_BASE_URI does not work Ayoub Zaki
2015-12-01 14:34 ` Leonardo Sandoval
2015-12-01 18:16   ` Paul Eggleton
2015-12-01 18:38     ` Leonardo Sandoval [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=565DE909.80007@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=ayoub.zaki@googlemail.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=srifenbark@gmail.com \
    --cc=yocto@yoctoproject.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 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.