From: Chong Lu <Chong.Lu@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH V3 0/2] bitbake-layers: add a ability to query layer dependencies from layer index
Date: Fri, 6 Feb 2015 14:52:14 +0800 [thread overview]
Message-ID: <54D4649E.7080403@windriver.com> (raw)
In-Reply-To: <1584081.qrVQXzTzW7@peggleto-mobl5.ger.corp.intel.com>
On 02/03/2015 12:05 AM, Paul Eggleton wrote:
> Hi Chong,
>
> On Friday 23 January 2015 13:28:32 Chong Lu wrote:
>> Change since V2:
>> re-split for IPv6 URL parsing
>>
>> The following changes since commit 35c9fa0588ed8e88b541a6c80cc1517324616cea:
>>
>> maintainers: Update for non-maintained recipes (2015-01-20 21:39:41 +0000)
>>
>> are available in the git repository at:
>>
>> git://git.pokylinux.org/poky-contrib chonglu/layerindex
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=chonglu/layerindex
>>
>> Chong Lu (2):
>> bitbake.conf: Add two variables for layer index
>> bitbake-layers: add a ability to query layer dependencies from layer index
> Apologies for the delay in getting back to you. This is definitely improving,
> some feedback though:
>
> * I think the new subcommand would make more sense if it were switched around
> so that it was fetching by default (and renamed as appropriate). Perhaps
> "layerindex-fetch" (with -n to avoid fetching and just report what it would
> fetch).
>
> * I think the layer index URL specified in the OE variable should be to the
> root rather than to /api - instead have that suffix added by the code that does
> the API calls. This makes it usable as a URL for the index for presenting to
> the user if needed.
>
> * Can you rename the two variables to BBLAYERS_LAYERINDEX_URL and
> BBLAYERS_FETCH_DIR (sorry I didn't think of this earlier).
I don't understand why does uname? Or, would you give me a example?
>
> * Please mention bitbake-layers in the comment above the settings in
> bitbake.conf so it's clear where these variables are used.
And I don't understand this one """
Please mention bitbake-layers in the comment above the settings in
bitbake.conf so it's clear where these variables are used.
"""
Would you explain in details?
Best Regards
Chong
>
> * By using -q with git you lose the status output which can be very useful
> given how long it can take to fetch some layers e.g. meta-oe, so can you drop
> this?
>
> * Can you add a check to see if the layer has already been fetched before
> fetching it and skip the fetch if it does (but not skip the add)?
>
> * If I run "bitbake-layers show-layer-deps meta-security" I get an error:
> ERROR: Can NOT get meta-security git repo and subdir
> (The code currently expects there to be a subdir, but this is an optional
> field, not all layers have a subdirectory, meta-security is one example.)
>
> * I think you may be able to get away with skipping the initial parse by
> passing config_only=True to init_bbhandler(). If you can, this will save a bit
> of time each time you run the command.
>
> Thanks,
> Paul
>
next prev parent reply other threads:[~2015-02-06 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 5:28 [PATCH V3 0/2] bitbake-layers: add a ability to query layer dependencies from layer index Chong Lu
2015-01-23 5:28 ` [PATCH V3 1/2] bitbake.conf: Add two variables for " Chong Lu
2015-01-23 5:28 ` [PATCH V3 2/2] bitbake-layers: add a ability to query layer dependencies from " Chong Lu
2015-01-23 13:30 ` Bernhard Reutner-Fischer
2015-01-30 1:20 ` [PATCH V3 0/2] " Chong Lu
2015-02-02 16:05 ` Paul Eggleton
2015-02-03 10:12 ` Paul Eggleton
2015-02-09 10:59 ` Paul Eggleton
2015-02-06 6:52 ` Chong Lu [this message]
2015-02-06 9:56 ` Paul Eggleton
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=54D4649E.7080403@windriver.com \
--to=chong.lu@windriver.com \
--cc=bitbake-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox