All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.
Date: Mon, 25 Jun 2018 08:18:54 +0100	[thread overview]
Message-ID: <575b002da9b0b86490a3eada07f254428549965e.camel@linuxfoundation.org> (raw)
In-Reply-To: <1529783581-46179-9-git-send-email-zhengrq.fnst@cn.fujitsu.com>

On Sun, 2018-06-24 at 03:53 +0800, Zheng Ruoqin wrote:
> Add dnf-nativesdk and it's runtime dependence to make dnf work on
> cross-development environment.
> 
> Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>

I don't mind adding enough of the changes so that dnf-nativesdk is
buildable so some of your other patches can be merged.

I do not want to add dnf-nativesdk to meta-toolchain by default however
as there are many people who don't need this there. I'd suggest this is
a customisation you'll need to maintain yourselves.

I appreciate why you want to do this, I also believe we have a better
technique in the form of the eSDK, where we can use the same tools and
the same codebase to build for example a rootfs.

The eSDK use case (a locked sstate cache) is designed so that a user
doesn't need to worry about a whole build, or building from scratch.
They can use the same tools everyone else uses and the same workflow
and code to bulld a rootfs or a recipe or any workflow. This makes it
much more powerful and able to fulfil many different use cases compared
to meta-toolchain. In the long run I'd therefore prefer we promote this
and use the eSDK as I think it will become our preferred way of
handling problems like this.

Cheers,

Richard


  reply	other threads:[~2018-06-25  7:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-23 19:52 [PATCH 0/8] [PATCH v2]meta-toolchain: Added dnf-nativesdk into cross-development toolchain Zheng Ruoqin
2018-06-23 19:52 ` [PATCH 1/8][PATCH v2] slang: add nativesdk Zheng Ruoqin
2018-06-23 19:52 ` [PATCH 2/8][PATCH v2] libnewt: Add nativesdk Zheng Ruoqin
2018-06-23 19:52 ` [PATCH 3/8][PATCH v2] libnewt-python: " Zheng Ruoqin
2018-06-23 19:52 ` [PATCH 4/8][PATCH v2] libnewt-python: Add PROVIDES for nativesdk Zheng Ruoqin
2018-06-25  7:10   ` Richard Purdie
2018-06-23 19:52 ` [PATCH 5/8][PATCH v2] createrepo-c: Add nativesdk Zheng Ruoqin
2018-06-23 19:52 ` [PATCH 6/8][PATCH v2] update-rc.d: " Zheng Ruoqin
2018-06-25  9:43   ` Burton, Ross
2018-06-25 10:05     ` Richard Purdie
2018-06-23 19:53 ` [PATCH 7/8] [PATCH v2] rpm: Add DEPENDS for nativesdk Zheng Ruoqin
2018-06-25  7:12   ` Richard Purdie
2018-06-23 19:53 ` [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain Zheng Ruoqin
2018-06-25  7:18   ` Richard Purdie [this message]
2018-07-31  2:18     ` Zheng, Ruoqin
2018-07-31 11:15       ` richard.purdie
2018-07-31 15:46         ` Alexander Kanavin

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=575b002da9b0b86490a3eada07f254428549965e.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=zhengrq.fnst@cn.fujitsu.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.