**** BEGIN LOGGING AT Sat Jan 07 03:00:02 2017
Jan 07 08:55:34 <ayaka> if I use recipetool create git@github.com:users/repo.git and forget to use -o option
Jan 07 08:56:10 <ayaka> it seems cost a long time to download the source code(network is slow) but without new recipe created
Jan 07 08:57:21 <ayaka> worry, it created a bb in the build
Jan 07 08:57:54 <ayaka> but if I want to create a recipe in the layer, should I use the abstract url to set the path?
Jan 07 17:23:01 <likewise> Is PACKAGECONFIG_pn-somepackage_remove = "removethisone" supported?
Jan 07 17:23:15 <likewise> ^ in local.conf
Jan 07 17:28:21 <nrossi> likewise: you need to do it the other way around, PACKAGECONFIG_remove_pn-somepackage, since "pn-somepackage" is an override
Jan 07 17:29:35 <likewise> nrossi: Ah thanks, let me try that. (I have strace, but due to DISTRO_FEATURES containing bluetooth, suddenly strace depends on bluez depends on x11).
Jan 07 17:32:21 <likewise> related: How can I verify what is the resulting PACKAGECONFIG the strace package uses?  I tried bitbake -e strace | grep PACKAGECONFIG (and the experimental bb tool: bb show -r strace PACKAGECONFIG) but they keep showing bluez, even when I empty PACKAGECONFIG as follows: PACKAGECONFIG_pn-strace = "" in local.conf
Jan 07 17:40:40 <likewise> works: PACKAGECONFIG_remove_pn-strace = "bluez"
Jan 07 17:40:58 <likewise> doesn't work:  PACKAGECONFIG_pn-strace = ""
Jan 07 17:41:31 <likewise> is this due to the order in which these variables get evaluated/expanded?  _remove is very late AFAIK
Jan 07 17:53:26 <nrossi> likewise: strace sets PACKAGECONFIG_class-target, which is higher priority than pn-strace
Jan 07 17:55:54 <nrossi> likewise: If you look at the full output in bitbake -e, it will tell you about the variable operations/overrides that are in play.
**** ENDING LOGGING AT Sun Jan 08 03:00:00 2017