Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Nosthoff <buildroot@heine.tech>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] package/systemd: unify journal remote options
Date: Wed, 14 Oct 2020 17:12:48 +0200	[thread overview]
Message-ID: <20201014151249.18330-1-buildroot@heine.tech> (raw)

this patch is the result of the discussion at [0] and fixes #12301.

I moved the libqrencode dependency in the first patch for two reasons:
 - it untangles the if-else construct for the remote part
 - in systemd 247 homectl will also be using libqrencode for recovery-keys [1]

In the second patch I deprecated the systemd-journal-gatewayd options as it is
now part of the systemd-journal-remote option. Also since the patch mentioned
in the discussion you already needed to set the latter to get gatewayd built.

[0] http://lists.busybox.net/pipermail/buildroot/2020-October/294477.html
[1] https://github.com/systemd/systemd/blob/master/src/home/homectl-recovery-key.c#L3

Michael Nosthoff (2):
  package/systemd: link libqrencode independent of remote
  package/systemd: group all journal-remote tools

 Config.in.legacy           |  7 +++++++
 package/systemd/Config.in  | 28 ++++++++++++----------------
 package/systemd/systemd.mk | 22 +++++++++-------------
 3 files changed, 28 insertions(+), 29 deletions(-)

-- 
2.25.1

             reply	other threads:[~2020-10-14 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 15:12 Michael Nosthoff [this message]
2020-10-14 15:12 ` [Buildroot] [PATCH 1/2] package/systemd: link libqrencode independent of remote Michael Nosthoff
2020-10-14 18:43   ` Thomas Petazzoni
2020-10-14 15:12 ` [Buildroot] [PATCH 2/2] package/systemd: group all journal-remote tools Michael Nosthoff

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=20201014151249.18330-1-buildroot@heine.tech \
    --to=buildroot@heine.tech \
    --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