From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/mender: new package
Date: Fri, 4 May 2018 09:23:46 +0200 [thread overview]
Message-ID: <20180504092346.6b5835db@windsurf> (raw)
In-Reply-To: <1525384358-26211-1-git-send-email-angelo@amarulasolutions.com>
Hello Angelo,
Thanks for pushing this further. We definitely want to have Mender.io
support in Buildroot, so it's great to see this make progress.
On Thu, 3 May 2018 23:52:38 +0200, Angelo Compagnucci wrote:
> package/mender/server.crt | 22 ++++++++++++++
Not a complete review by far, but I'm wondering if it makes sense to
include server certificates in Buildroot. I would assume that one would
want to generate his own certificate instead, no ?
> diff --git a/package/mender/Config.in b/package/mender/Config.in
> new file mode 100644
> index 0000000..b80ad4a
> --- /dev/null
> +++ b/package/mender/Config.in
> @@ -0,0 +1,14 @@
> +config BR2_PACKAGE_MENDER
> + bool "mender"
> + depends on BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS
> + depends on BR2_PACKAGE_HOST_GO_CGO_LINKING_SUPPORTS
> + depends on BR2_TOOLCHAIN_HAS_THREADS
> + depends on BR2_INIT_SYSTEMD
Is there anything that makes mender tied to systemd, other than the
fact that you provide only a systemd mender.service, and no init
script ?
> +
Unneeded empty new line.
> +define MENDER_INSTALL_TARGET_CMDS
> + $(INSTALL) -dm 0755 $(TARGET_DIR)/etc/mender/
> + $(INSTALL) -dm 0755 $(TARGET_DIR)/var/share/mender/identity/
> + $(INSTALL) -dm 0755 $(TARGET_DIR)/var/share/mender/inventory/
These commands are not needed: the $(INSTALL) -D below, with full
destination paths, will create the intermediate directories if they
don't already exist.
> + $(INSTALL) -D -m 0644 package/mender/mender.conf \
> + $(TARGET_DIR)/etc/mender/mender.conf
> + $(INSTALL) -D -m 0644 package/mender/tenant.conf \
> + $(TARGET_DIR)/etc/mender/mender.conf
Are you sure that installing tenant.conf as mender.conf is what you
want to do here ?
> + $(INSTALL) -D -m 0644 package/mender/server.crt \
> + $(TARGET_DIR)/etc/mender/server.crt
> + $(INSTALL) -D -m 0755 package/mender/mender-device-identity \
> + $(TARGET_DIR)/var/share/mender/identity/mender-device-identity
> + $(INSTALL) -D -m 0755 package/mender/mender-inventory-network \
> + $(TARGET_DIR)/var/share/mender/inventory/mender-inventory-network
> + $(INSTALL) -D -m 0755 package/mender/mender-inventory-hostinfo \
> + $(TARGET_DIR)/var/share/mender/inventory/mender-inventory-hostinfo
> + $(INSTALL) -D -m 0644 package/mender/mender.service \
> + $(TARGET_DIR)/usr/lib/systemd/system/mender.service
Is this enough to enable the systemd service ? In most packages, we do
a dance like this:
define OLSR_INSTALL_INIT_SYSTEMD
$(INSTALL) -D -m 644 package/olsr/olsr.service \
$(TARGET_DIR)/usr/lib/systemd/system/olsr.service
mkdir -p $(TARGET_DIR)/etc/systemd/system/multi-user.target.wants
ln -sf ../../../../usr/lib/systemd/system/olsr.service \
$(TARGET_DIR)/etc/systemd/system/multi-user.target.wants/olsr.service
endef
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-04 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 21:52 [Buildroot] [PATCH v2] package/mender: new package Angelo Compagnucci
2018-05-04 7:23 ` Thomas Petazzoni [this message]
2018-05-04 9:09 ` Angelo Compagnucci
2018-05-04 9:16 ` Thomas Petazzoni
2018-05-04 9:20 ` Angelo Compagnucci
-- strict thread matches above, loose matches on Subject: below --
2018-06-04 21:37 Dan Walkes
2018-06-05 7:33 ` Thomas Petazzoni
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=20180504092346.6b5835db@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