Am 20.02.2025 um 11:00 schrieb Richard Purdie via lists.openembedded.org:
On Thu, 2025-02-20 at 10:48 +0100, Stefan Herbrechtsmeier wrote:
Am 19.02.2025 um 18:33 schrieb Richard Purdie:
On Wed, 2025-02-19 at 17:48 +0100, Stefan Herbrechtsmeier wrote:
I don't change the exception. The exceptions
On Thu, 2025-02-20 at 10:48 +0100, Stefan Herbrechtsmeier wrote:
>
> Am 19.02.2025 um 18:33 schrieb Richard Purdie:
> >
> > On Wed, 2025-02-19 at 17:48 +0100, Stefan Herbrechtsmeier wrote:
> > >
> > >
> > >
> > > I don't change the exception. The exceptions are the reason for
> > > the sta
Am 19.02.2025 um 18:33 schrieb Richard Purdie:
On Wed, 2025-02-19 at 17:48 +0100, Stefan Herbrechtsmeier wrote:
I don't change the exception. The exceptions are the reason for the
state of the series.
The missing point is that the expectation is related to the end of a
dependency chain and n
On Wed, 2025-02-19 at 17:48 +0100, Stefan Herbrechtsmeier wrote:
>
> I don't change the exception. The exceptions are the reason for the
> state of the series.
>
> The missing point is that the expectation is related to the end of a
> dependency chain and not to a task itself. In any case the re
Am 17.02.2025 um 18:29 schrieb Richard Purdie:
FWIW I did try and discuss this in the OE TSC meeting today but it is a
US holiday. There were only two people who showed up.
I answer your points below but does it make sense to create a RFC to
show how an alternative source URI management in oe-
On Mon, Feb 17, 2025 at 12:29 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> FWIW I did try and discuss this in the OE TSC meeting today but it is a
> US holiday. There were only two people who showed up.
>
Also a Canadian Holiday! I was one of the missing attendees, so I'll fol
FWIW I did try and discuss this in the OE TSC meeting today but it is a
US holiday. There were only two people who showed up.
On Mon, 2025-02-17 at 17:38 +0100, Stefan Herbrechtsmeier wrote:
> Am 17.02.2025 um 13:43 schrieb Richard Purdie:
> On Mon, 2025-02-17 at 12:00 +0100, Stefan Herbrechtsme
Am 17.02.2025 um 13:43 schrieb Richard Purdie:
On Mon, 2025-02-17 at 12:00 +0100, Stefan Herbrechtsmeier wrote:
Am 13.02.2025 um 11:43 schrieb Richard Purdie via lists.openembedded.org:
e) add the ability to add custom hooks in the fetch process to
handle
the cases of needing to alter the
On Mon, 2025-02-17 at 12:00 +0100, Stefan Herbrechtsmeier wrote:
> Am 13.02.2025 um 11:43 schrieb Richard Purdie via lists.openembedded.org:
>
> > e) add the ability to add custom hooks in the fetch process to
> > handle
> > the cases of needing to alter the flow for patching the components
> >
Am 13.02.2025 um 11:43 schrieb Richard Purdie via lists.openembedded.org:
e) add the ability to add custom hooks in the fetch process to handle
the cases of needing to alter the flow for patching the components list
I fear this isn't easy possible and we have a design problem. Bitbake
and oe-c
Am 13.02.2025 um 21:32 schrieb Richard Purdie:
On Thu, 2025-02-13 at 17:33 +0100, Stefan Herbrechtsmeier wrote:
Am 13.02.2025 um 11:43 schrieb Richard Purdie via lists.openembedded.org:
Most of the concerns I've seen are about how easy it is to understand
what is going on behind the scenes.
On Thu, 2025-02-13 at 17:33 +0100, Stefan Herbrechtsmeier wrote:
> Am 13.02.2025 um 11:43 schrieb Richard Purdie via lists.openembedded.org:
>
> > Most of the concerns I've seen are about how easy it is to understand
> > what is going on behind the scenes. The move of code to OE and
> > splitting
Am 13.02.2025 um 11:43 schrieb Richard Purdie via lists.openembedded.org:
I've pulled this to a separate email/thread since I'd like to take a
slight step back and put some different ideas into the mix as well as
explain where my own thoughts are right now. I'm also doing this so
that we can focu
13 matches
Mail list logo
