On 1 Aug 2016, at 17:55, Richard Purdie wrote:
The trouble is that for speed, we do create trees of hardlinked files
and play games with those and sstate amongst other things.
Yeah. One concern would be ownership: If the things we're hardlinking to
weren't created/tracked by pseudo initially, they're going to show up as
owned by the actual user doing the build. So hardlinks to them will
also.
So it may be more reasonable to just create those things under pseudo
also, in which case they're already tracked.
Its
obviously faster to do this than make physical copies of the files.
Given what I know of the code paths, I suspect that tracking the
source
of a hardlink would make life much easier for us. Obviously we can go
and start adding "chown -R" calls everywhere but that seems a little
ugly to me and doesn't do performance any favours.
Is there any significant downside if we do track the source of
hardlinks?
Hmm. I'm not sure. It'll make things more complicated, but only
marginally. The net impact would be fewer surprises in common cases, but
the uncommon cases would get *really* weird. But it seems reasonable.
(At least for the case where there isn't an existing entry.) I'll
poke at this a bit, I think.
-s
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
