From: "Ahmad Fatoum" <a.fatoum@pengutronix.de>
To: Nathan Rossi <nathan@nathanrossi.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] vim: add nativesdk to BBCLASSEXTEND
Date: Thu, 5 Nov 2020 10:49:53 +0100 [thread overview]
Message-ID: <6f81e2cc-4885-e738-8f36-cab6d3b291ac@pengutronix.de> (raw)
In-Reply-To: <CA+aJhH1BM+PmLEKPyQnUYLX8MLkh9gNFKa5oewsZY-bmpgxGfg@mail.gmail.com>
Hello,
On 11/5/20 2:30 AM, Nathan Rossi wrote:
> On Wed, 4 Nov 2020 at 23:32, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>> On 11/4/20 2:17 PM, Nathan Rossi wrote:
>>> Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
>>> ---
>>> meta/recipes-support/vim/vim_8.2.bb | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/meta/recipes-support/vim/vim_8.2.bb b/meta/recipes-support/vim/vim_8.2.bb
>>> index 709b6ddb55..7e4654e472 100644
>>> --- a/meta/recipes-support/vim/vim_8.2.bb
>>> +++ b/meta/recipes-support/vim/vim_8.2.bb
>>> @@ -3,7 +3,7 @@ require vim.inc
>>> PROVIDES = "xxd"
>>>
>>> PACKAGECONFIG_class-native = ""
>>> -BBCLASSEXTEND = "native"
>>> +BBCLASSEXTEND = "native nativesdk"
>>
>> Apologies if this is self-evident, but why should nativesdk be added here?
>
> It should be added so that vim can be included as part of a
> buildtools-tarball/sdk. It is useful to be able to provide an editor
> in a relatocable form, for when hosts do not provide an editor. It is
> also useful for the xxd tool.
I see. Thanks!
>> A commit message explaining the why would be quite helpful.
>
> Sorry, I've made quite a few of these mechanical add nativesdk patches
> recently, and in the past. The reason for the change is almost always
> for sdk/buildtools-tarball. I can add the above description if that
> explanation is sufficient?
I'd appreciate that. I am trying to read along to get more familiar with OE
and commit messages make this considerably easier.
Cheers,
Ahmad
>
> Regards,
> Nathan
>
>>
>>>
>>> ALTERNATIVE_${PN}_append = " xxd"
>>> ALTERNATIVE_TARGET[xxd] = "${bindir}/xxd"
>>> ---
>>> 2.28.0
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> Pengutronix e.K. | |
>> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
>> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2020-11-05 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 13:17 [PATCH] vim: add nativesdk to BBCLASSEXTEND Nathan Rossi
2020-11-04 13:32 ` [OE-core] " Ahmad Fatoum
2020-11-05 1:30 ` Nathan Rossi
2020-11-05 9:49 ` Ahmad Fatoum [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=6f81e2cc-4885-e738-8f36-cab6d3b291ac@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=nathan@nathanrossi.com \
--cc=openembedded-core@lists.openembedded.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