> > FWIW: We created a proprietary license file called files/common-
> > licenses/company.txt in our proprietary layer, then added the
> > following to layer.conf:
> >
> > COMPANY_COMMON_LICENSES := '${@os.path.normpath("${LAYERDIR}/files
> > /com
> > mon-licenses")}'
> > BB_HASHBASE_WHITELIST
On Fri, 2017-06-16 at 11:00 -0700, Khem Raj wrote:
> On 6/16/17 6:14 AM, Joshua Watt wrote:
> > On Fri, 2017-06-16 at 09:12 +, Thomas Thorne wrote:
> > > > > Is it only possible to use the special
> > > > > LICENSE = "CLOSED"
> > > > > license for licenses not already placed in the main license
On 6/16/17 6:14 AM, Joshua Watt wrote:
> On Fri, 2017-06-16 at 09:12 +, Thomas Thorne wrote:
Is it only possible to use the special
LICENSE = "CLOSED"
license for licenses not already placed in the main license
>> directory?
>>>
>>> Yes, there's special-case logic for 'CLOSED'.
On Fri, 2017-06-16 at 09:12 +, Thomas Thorne wrote:
> >> Is it only possible to use the special
> >> LICENSE = "CLOSED"
> >> license for licenses not already placed in the main license
> directory?
> >
> > Yes, there's special-case logic for 'CLOSED'. Can you not just use
> that for your inter
>> Is it only possible to use the special
>> LICENSE = "CLOSED"
>> license for licenses not already placed in the main license directory?
>
> Yes, there's special-case logic for 'CLOSED'. Can you not just use that for
> your internal pieces? It's special-cased in a few places.
I can use CLOSED.
Hi,
On 2017-06-15 17:52, Thomas A. F. Thorne MEng AUS MIET wrote:
Good afternoon,
I am putting together a meta-company-name layer to hold some internal
code. This will contain a few BSPs for our units, some internally
developed applications and a few config file patches. I am having
trouble g
On 15 June 2017 at 15:52, Thomas A. F. Thorne MEng AUS MIET <
thomas.tho...@net2edge.com> wrote:
> Is it only possible to use the special
> LICENSE = "CLOSED"
> license for licenses not already placed in the main license directory?
>
Yes, there's special-case logic for 'CLOSED'. Can you not just
Good afternoon,
I am putting together a meta-company-name layer to hold some internal
code. This will contain a few BSPs for our units, some internally
developed applications and a few config file patches. I am having
trouble getting recipes to be related to the proprietary license.
I have ad
