From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/mender: new package
Date: Tue, 5 Jun 2018 09:33:44 +0200 [thread overview]
Message-ID: <20180605093344.23db50a9@windsurf> (raw)
In-Reply-To: <CAAhKrJ04tvAMGuhPsTjPo-56FvD+Pt0BRBuKysveTTLMHoM1Tg@mail.gmail.com>
Hello,
On Mon, 4 Jun 2018 15:37:52 -0600, Dan Walkes wrote:
> Thanks for providing this patch. I'm also interested in buildroot
> support for mender.
Great! Thanks for your comments and feedback on the Mender integration,
definitely useful.
> I expect it's just that they only test integration with systemd and
> systemd is not a requirement. See the comment at [1] from Mirza Krak
> on the Mender dev team.
>
> > Mender does not have a hard-requirement on systemd (BR2_INIT_SYSTEMD), there is only a conveniently provided systemd service by default.
>
> I've started with the patch at [2], then made a few small changes to
> get the package running on an x86 qemu virtual machine with default
> sysv init scripts. See the project at [3] and branch at [4] for
> details.
Great. Perhaps I could merge Angelo's patch, and you could send
follow-up patch improving it, such as providing non-systemd
integration ?
> For some reason I don't understand, I needed to add a step to
> specifically install the binary after the golang build, it wasn't
> happening by default for me. See the patch at [5].
>
> I've noticed the current mender patches do not have support for
> mender-artifact today. In order to build the mender artifact utility
> I think I'd need to build a host golang package based on mender
> artifact [6] but it looks like only target packages are currently
> supported today with pkg-golang buildroot [7], is that correct? How
> should I build the mender-artifact utility for the host?
The pkg-golang infrastructure should probably be extended to build host
packages as well. So far it wasn't needed, but if it's needed, then
let's do it.
> What would
> be the correct way to invoke the mender-artifact utility to actually
> generate the artifact? Would this be done through a custom post-image
> script?
Yes, that's generally the idea for tools that generate some kind of
firmware image.
> Has work already started on mender-artifact support in another patch
> or on a branch somewhere?
Everything submitted to the Buildroot mailing list is recorded in our
patch tracking system
(https://patchwork.ozlabs.org/project/buildroot/list/). And no, there's
no work on mender-artifact support that has been submitted, at least
not that I remember.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-05 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 21:37 [Buildroot] [PATCH v2] package/mender: new package Dan Walkes
2018-06-05 7:33 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-03 21:52 Angelo Compagnucci
2018-05-04 7:23 ` Thomas Petazzoni
2018-05-04 9:09 ` Angelo Compagnucci
2018-05-04 9:16 ` Thomas Petazzoni
2018-05-04 9:20 ` Angelo Compagnucci
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=20180605093344.23db50a9@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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