[OE-core] Status of usrmerge merger

2017-03-18 Thread Anton Gerasimov
Hi, what is the current status of the usrmerge patch [1]? It was submitted quite a long time ago and I can't find any discussion about it. If there is something I can do to help with testing/tweaking to get it merged please let me know. Thanks, Anton Gerasimov [1] https://patchwork.openembedded.

Re: [OE-core] Hints on submitting to OE-Core

2017-03-18 Thread Daniel Dickinson
On Sat, 18 Mar 2017 01:42:06 -0700 akuster808 wrote: > On 03/17/2017 06:21 PM, Gary Thomas wrote: > > On 2017-03-18 00:55, Daniel Dickinson wrote: > >> Hi all, > >> > >> I've got a pre-alpha 'distro' and some layers I think that could > >> get to an interesting state. The intent is to work the

Re: [OE-core] Hints on submitting to OE-Core

2017-03-18 Thread Daniel Dickinson
On Sat, 18 Mar 2017 01:42:06 -0700 akuster808 wrote: > On 03/17/2017 06:21 PM, Gary Thomas wrote: > > On 2017-03-18 00:55, Daniel Dickinson wrote: > >> Hi all, > >> > >> I've got a pre-alpha 'distro' and some layers I think that could > >> get to an interesting state. The intent is to work the

[OE-core] [PATCH 2/2] bitbake.conf: remove vi from HOSTTOOLS list

2017-03-18 Thread brian avery
Having changes the sdk test to cpio from cvs, we no longer require an editor to be present. This patch removes vi from the list of required tools. Signed-off-by: brian avery --- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/conf/bitbake.conf b/me

[OE-core] [PATCH 1/2] meta/lib/oeqa: change sdk test from cvs to cpio

2017-03-18 Thread brian avery
We currently fetch,configure,build, and install cvs as our test for the sdk. cvs unfortunately, requires a default editor in order to run. The change in 94790a8254d6 that checks to see if you have something like vi installed is fragile since you may have a different default editor. This patch swi

[OE-core] [PATCH 0/2] testsdk: use cpio instead of cvs as test

2017-03-18 Thread brian avery
We were using cvs as our sdk test by running configure,make, and install using the sdk. Unfortunately, cvs requires vi and we were therefore requiring vi as one of our HOSTTOOLS. Since this is a choice among many for editors, it makes for a fragile requirement. Furthermore, a build container wo

[OE-core] [PATCH 0/2] testsdk: use cpio instead of cvs as test

2017-03-18 Thread brian avery
We were using cvs as our sdk test by running configure,make, and install using the sdk. Unfortunately, cvs requires vi and we were therefore requiring vi as one of our HOSTTOOLS. Since this is a choice among many for editors, it makes for a fragile requirement. Furthermore, a build container wo

Re: [OE-core] Hints on submitting to OE-Core

2017-03-18 Thread akuster808
On 03/17/2017 06:21 PM, Gary Thomas wrote: On 2017-03-18 00:55, Daniel Dickinson wrote: Hi all, I've got a pre-alpha 'distro' and some layers I think that could get to an interesting state. The intent is to work them up to where they are suitable to be submitted as patches to oe-core rather