All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: "Zheng, Ruoqin" <zhengrq.fnst@cn.fujitsu.com>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 8/8] [PATCH v2] meta-toolchain: Added dnf-nativesdk into cross-development toolchain.
Date: Tue, 31 Jul 2018 12:15:47 +0100	[thread overview]
Message-ID: <619fe34cca9bc682823913d12cc88486f8458d72.camel@linuxfoundation.org> (raw)
In-Reply-To: <33D4DBCAC5F2D74E96B07F6E7632BF738709F509@G08CNEXMBPEKD01.g08.fujitsu.local>

On Tue, 2018-07-31 at 02:18 +0000, Zheng, Ruoqin wrote:
> Hi Richard
> 
>       eSDK is actually a better technique for developers.  But it’s
> only suitable for those people who has experience on Yocto Project.

Remember that the eSDK can function just like the SDK. You can use more
of its tools but you don't have to.

>       In the other hand, using dnf-nativesdk in meta-toolchain to
> customize rootfs is easier fot those people who are familiar with
> dnf(I think most linux user known it).

Why not add some dnf like wrappers around the eSDK though? We have
tools like devtool and recipetool but there is a lot of potential to
add a simpler interface to enable these "customise rootfs" type of
workflows.

>       For example, developers finish the OSS build work and provide
> the toolchain and packages to users. In this case, users do not need
> to know any knowledge about yocto build system but just how to use
> dnf to install a rootfs.
> 
>       So it can reduce the workload of end-users who need to
> customize rootfs for their embedded device. At lease, they don’t need
> to maintain a yocto build server.

The eSDK behaves very much like the SDK and then you have access to
whichever tools the eSDK is providing, all the way up to the full build
system but only if you need that.

I still think there is the option of providing some simpler tooling to
the eSDK which would work for the kinds of users you're talking about.

Cheers,

Richard



  reply	other threads:[~2018-07-31 11:15 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
2018-07-31  2:18     ` Zheng, Ruoqin
2018-07-31 11:15       ` richard.purdie [this message]
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=619fe34cca9bc682823913d12cc88486f8458d72.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.