On Tuesday, 3 December 2019 3:46:00 AM NZDT Mark Hatle wrote:
> On 12/2/19 8:30 AM, Martin Jansa wrote:
> > Even if the original URL isn't available anymore there might be some
> > existing
> > forks on github or elsewhere.
>
> But how would someone find it, and if they did find a fork how would
Taking just this part of the discussion for now (since it is a small familiar
aspect to me)
On Tuesday, 3 December 2019 1:08:54 PM NZDT Mark Hatle wrote:
> > You may want to consider this now. Adding system with the "nomachine"
> > mode you mention is a nightmare scenario for parsing. Bitbake
On 12/2/19 5:53 PM, Richard Purdie wrote:
> On Mon, 2019-12-02 at 17:19 -0600, Mark Hatle wrote:
>>
>> On 12/2/19 3:58 PM, Richard Purdie wrote:
>>> On Mon, 2019-12-02 at 15:37 -0600, Mark Hatle wrote:
In all of the above examples, the user has manually configured
the
multiconfig
On 12/2/19 5:47 PM, Richard Purdie wrote:
> On Mon, 2019-12-02 at 15:27 -0800, Alejandro Enedino Hernandez
> Samaniego wrote:
>> So I have tried something similar to this, and while it does work,
>> due to some parsing issue (I still have not figured out exactly what)
>> the multiconfig
On Mon, 2019-12-02 at 17:19 -0600, Mark Hatle wrote:
>
> On 12/2/19 3:58 PM, Richard Purdie wrote:
> > On Mon, 2019-12-02 at 15:37 -0600, Mark Hatle wrote:
> > > In all of the above examples, the user has manually configured
> > > the
> > > multiconfig within their project. There is a simple way
On Mon, 2019-12-02 at 15:27 -0800, Alejandro Enedino Hernandez
Samaniego wrote:
> So I have tried something similar to this, and while it does work,
> due to some parsing issue (I still have not figured out exactly what)
> the multiconfig dependencies between multiconfigs are not being taken
>
Hey guys,
On Mon, Dec 2, 2019 at 3:24 PM Mark Hatle
wrote:
>
>
> On 12/2/19 4:09 PM, Richard Purdie wrote:
> > On Mon, 2019-12-02 at 21:58 +, Richard Purdie wrote:
> >> On Mon, 2019-12-02 at 15:37 -0600, Mark Hatle wrote:
> >>> In all of the above examples, the user has manually configured
On 12/2/19 4:09 PM, Richard Purdie wrote:
> On Mon, 2019-12-02 at 21:58 +, Richard Purdie wrote:
>> On Mon, 2019-12-02 at 15:37 -0600, Mark Hatle wrote:
>>> In all of the above examples, the user has manually configured the
>>> multiconfig within their project. There is a simple way to
On 12/2/19 3:58 PM, Richard Purdie wrote:
> On Mon, 2019-12-02 at 15:37 -0600, Mark Hatle wrote:
>> In all of the above examples, the user has manually configured the
>> multiconfig within their project. There is a simple way to move that
>> configuration to a layer, simply place it in a
On Mon, 2019-12-02 at 21:58 +, Richard Purdie wrote:
> On Mon, 2019-12-02 at 15:37 -0600, Mark Hatle wrote:
> > In all of the above examples, the user has manually configured the
> > multiconfig within their project. There is a simple way to move
> > that
> > configuration to a layer, simply
Problem Statement
-
In the current world there is an increasing number of heterogeneous
systems being developed. Currently these components can be built
independently of each other, and then combined later. For ease of use,
it would be nice to be able to build these systems with
On 12/2/19 8:30 AM, Martin Jansa wrote:
> Even if the original URL isn't available anymore there might be some existing
> forks on github or elsewhere.
But how would someone find it, and if they did find a fork how would they know
it's 'authentic', i.e. not maliciously tampered with?
It's one
On 12/1/19 10:52 PM, akuster808 wrote:
>
>
> On 12/1/19 1:47 PM, Mark Hatle wrote:
>> I've been looking through the layer index (master primarly), and I think we
>> need
>> to figure out a policy of when to remove a layer from master indexing.
>>
>> So I'd like to suggest the following
On Sun, Dec 01, 2019 at 04:20:45PM -0600, Mark Hatle wrote:
>
>
> On 12/1/19 4:01 PM, Adrian Bunk wrote:
> > On Sun, Dec 01, 2019 at 03:47:43PM -0600, Mark Hatle wrote:
> >> ...
> >> After 18 months, the layer is clearly no longer being
> >> maintained and will cause more confusion then actually
14 matches
Mail list logo
