Re: [OE-core] [PATCH v3 1/2] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Alexander Kanavin
On 11/15/2017 05:10 PM, Martyn Welch wrote: Sometimes we wish to ensure that files or directories are not installed somewhere that may prove detrimental to the operation of the system. For example, this may be the case if files are placed in a directory that is utilised as a mount point at run ti

Re: [OE-core] [PATCH v3 1/2] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Martyn Welch
On Wed, 2017-11-15 at 18:46 -0200, Otavio Salvador wrote: > On Wed, Nov 15, 2017 at 1:10 PM, Martyn Welch > wrote: > > Sometimes we wish to ensure that files or directories are not installed > > somewhere that may prove detrimental to the operation of the system. For > > example, this may be the c

Re: [OE-core] [PATCH v3 1/2] image.bbclass: add prohibited-paths QA test

2017-11-16 Thread Martyn Welch
On Wed, 2017-11-15 at 18:46 -0200, Otavio Salvador wrote: > On Wed, Nov 15, 2017 at 1:10 PM, Martyn Welch > wrote: > > Sometimes we wish to ensure that files or directories are not installed > > somewhere that may prove detrimental to the operation of the system. For > > example, this may be the c

Re: [OE-core] [PATCH v3 1/2] image.bbclass: add prohibited-paths QA test

2017-11-15 Thread Otavio Salvador
On Wed, Nov 15, 2017 at 1:10 PM, Martyn Welch wrote: > Sometimes we wish to ensure that files or directories are not installed > somewhere that may prove detrimental to the operation of the system. For > example, this may be the case if files are placed in a directory that is > utilised as a mount

[OE-core] [PATCH v3 1/2] image.bbclass: add prohibited-paths QA test

2017-11-15 Thread Martyn Welch
Sometimes we wish to ensure that files or directories are not installed somewhere that may prove detrimental to the operation of the system. For example, this may be the case if files are placed in a directory that is utilised as a mount point at run time, thus making them inaccessible once when th