From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: "Karicheri, Murali" <Murali.Karicheri@sandc.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] creating packages for opkg for buildroot based embedded platform software
Date: Tue, 11 Jan 2022 18:13:15 +0200 [thread overview]
Message-ID: <87o84iw8qc.fsf@tarshish> (raw)
In-Reply-To: <DM5PR02MB32914F0603DC48BC02D1CA328A519@DM5PR02MB3291.namprd02.prod.outlook.com>
Hi Murali,
On Tue, Jan 11 2022, Karicheri, Murali wrote:
> Hello, buildroot experts,
>
> I am new to buildroot and was working with a buildroot expert for migrating
> our yocto based build system to use buildroot. Unfortunately, he has left our
> company for another oppotunity. Ever since I have started using buildroot for
> our build, I am very happy with its simplicity compared to yocto based build
> system. However, I have learned that buildroot expect the entire rootfs to be
> updated on a running system for updating fixes which is very expensive for
> deployment where there is limited bandwidth available to update the system. So
> that is the challenge that I am facing. Good news is opkg tools are supported
> in buildroot which is good. Typically, we would like to let our customer do
> periodic update to the system to have vulnerability fixes and other fixes
> released by buildroot. For example, let us say we base our system on
> 2021.02.x. So, when there is a maintenance update to this branch say,
> 2021.02.06, we would like to create an ipk file with the changes and provide
> that for syst
> em update. Idea is the file will be smaller and thus requires less bandwidth
> and will result in quicker update to the system. Do you have information on
> any project that is working to create a package manager for systems that uses
> buildroot for their build?
>
> My research showed one resource but is for open embedded or yocto or openwrt
> and is here. https://raymii.org/s/tutorials/Building_IPK_packages_by_hand.html
>
> Do you think this is what I should try or any other relevant information on this topic?
This Buildroot FAQ is relevant:
https://buildroot.org/downloads/manual/manual.html#faq-no-binary-packages
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-11 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 16:01 [Buildroot] creating packages for opkg for buildroot based embedded platform software Karicheri, Murali
2022-01-11 16:13 ` Baruch Siach via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-11 17:37 Karicheri, Murali
2022-01-13 12:18 ` Charles Steinkuehler
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=87o84iw8qc.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=Murali.Karicheri@sandc.com \
--cc=baruch@tkos.co.il \
/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