From: Hongxu Jia <hongxu.jia@windriver.com>
To: <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] package.bbclass: only one hardlink of separated debug info file in each directory
Date: Fri, 24 Aug 2018 17:11:22 +0800 [thread overview]
Message-ID: <d0743f1d-b7e2-10a5-7521-88ab3eda7bf3@windriver.com> (raw)
In-Reply-To: <8ab2dfe5f21ed72bbf4da87126e6172b6d413ee2.camel@linuxfoundation.org>
On 2018年08月24日 16:39, richard.purdie@linuxfoundation.org wrote:
> On Fri, 2018-08-24 at 15:16 +0800, Hongxu Jia wrote:
>> Hi RP,
>>
>> With this fix, we could not use yesterday's workaround fix
>> `git: create symlink rather than hardlink between bin/ and libexec/',
>>
>> But it is no harm for us, btw, Ubuntu use symlink in git , and Fedora
>> use hardlink in git
> Thanks, I was thinking there probably was a problem in package.bbclass
> which your change to git was working around and you've now fixed it!
>
> I think I'd prefer to leave git using hardlinks so that we can
> potentially spot problems like this in future. There are other recipes
> that use hardlinks where the breakage may be more subtle (e.g.
> e2fsprogs) so having some recipes using hardlinks is good.
>
> I wondered if you'd fancy creating a new additional oqea test for this
> debug hardlink issue so that we'd detect any problems in future? The
> test I added was:
>
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=318595754b66e8e4f3db1bce1ac086a2409e2eca
>
> and with the addition of a few directories, it could probably be extended?
Got it, I am very pleasure to do it, I will extend the case with
multiple dirs
//Hongxu
> Cheers,
>
> Richard
>
>
>
>
prev parent reply other threads:[~2018-08-24 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 7:00 [PATCH] package.bbclass: only one hardlink of separated debug info file in each directory Hongxu Jia
2018-08-24 7:16 ` Hongxu Jia
2018-08-24 8:39 ` richard.purdie
2018-08-24 9:11 ` Hongxu Jia [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d0743f1d-b7e2-10a5-7521-88ab3eda7bf3@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox