Re: [PATCH] lib/oe/path: try hardlinking instead of guessing when it might fail

[Henning Schild <henning.schild@siemens.com>]

On Mon, 6 Apr 2020 12:03:47 +0200
"[ext] Henning Schild" <henning.schild@siemens.com> wrote:

> On Mon, 6 Apr 2020 09:51:23 +0200
> Jan Kiszka <jan.kiszka@siemens.com> wrote:
> 
> > On 06.04.20 09:42, Henning Schild wrote:  
> > > On Sun, 5 Apr 2020 18:58:16 +0200
> > > Baurzhan Ismagulov <ibr@radix50.net> wrote:
> > >     
> > >> Hello Henning,
> > >>
> > >> On Fri, Jan 24, 2020 at 02:51:00PM +0100, Henning Schild wrote:
> > >>   
> > >>> This is related to fixing an issue with "--exclude-path" in wic.
> > >>> On the Isar side i have everything in place and might send it.
> > >>> But we need that upstream fix ... or some workaround if that
> > >>> does not get merged.    
> > >>
> > >> Do I understand correctly, you'd be providing a lib/oe update for
> > >> Isar along with the other necessary changes? A test case for
> > >> --exclude-path would be nice.    
> > > 
> > > The test-case is already somewhere in a branch of mine ;). The
> > > problem now is that this upstream fix need to come down into Isar.
> > > 
> > > But i am afraid that our lib/oe is a fork, miles away from
> > > upstream.    
> > 
> > We are fairly close, picking patches from upstream is often
> > possible when we aren't. I just did that not long ago 
> > (9813e9e821cb2c4f0ea66544e35030fa261f1a47). Some bits may have to
> > remain different sometimes, though.  
> 
> Ok, i will try a backport and send that test-case along with it.

Just sent something that fixes and tests in the future.

Henning

> Henning
> 
> > Jan
> >   
>