All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norbert Lange <nolange79@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 2/2] package/systemd: allow package to be used without init system
Date: Thu, 21 Jul 2022 16:59:49 +0200	[thread overview]
Message-ID: <CADYdroMqpgyCR0jyWdXR+UqiOSoNdKNN3OsGSSXDrBvR_RSyNw@mail.gmail.com> (raw)
In-Reply-To: <20220719154504.GJ2249625@scaer>

Am Di., 19. Juli 2022 um 17:45 Uhr schrieb Yann E. MORIN
<yann.morin.1998@free.fr>:
>
> Norbert, All,
>
> On 2022-07-19 15:16 +0200, Norbert Lange spake thusly:
> > Allow systemd to be built as normal package, this for example
> > allows building systemd-boot without any init system.
>
> How has the situation with upstream evolved since last time the topic
> was raised here:
>     https://lore.kernel.org/buildroot/cover.1545814334.git.yann.morin.1998@free.fr/#t
> and especially the sub-thread:
>     https://lore.kernel.org/buildroot/d38239f86f99924e87dcb6e045b2de3ac0cb435f.1545814334.git.yann.morin.1998@free.fr/
>
> As far as I know (and understand), upstream has decided to tie the build
> of systemd-boot (formerly the standalone gummiboot) to the build of the
> rest of the systemd suite; they did not accept to make it possible to
> only build systemd-boot to use it outside the systemd ecosystem.
>
> From Buildroot's perspective, allowing to build systemd without it being
> an init system, and without the possibility to just build systemd-boot,
> is asking for troubles down the line.
>
> The triviality of your patch does not make it possible to only just
> build systemd-boot; instead, it still builds the whole systemd suite,
> which hints that upstream did not make it possible to do separate
> builds.

This was an example, and I do just that, even you built more than just
systemd-boot, picking "no init" speeds things up a bit.

> So, unless things have evolved substantially, I am not very fond of
> alowing this, and stand by the decision that was made back then (i.e.
> abide by upstream decision and tie systemd-boot to the systemd
> ecosystem).

I want to build systemd without using it as init system. Is there any
reason to artificially prohibit that?
It's just a regular package for me.

Norbert
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-07-21 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 13:16 [Buildroot] [PATCH 1/2] package/systemd: allow empty SYSTEMD_DEFAULT_TARGET Norbert Lange
2022-07-19 13:16 ` [Buildroot] [PATCH 2/2] package/systemd: allow package to be used without init system Norbert Lange
2022-07-19 15:45   ` Yann E. MORIN
2022-07-21 14:59     ` Norbert Lange [this message]
2022-07-22 21:23       ` Arnout Vandecappelle
2022-07-22 21:29     ` Arnout Vandecappelle
2022-07-23 10:34       ` Arnout Vandecappelle
2022-07-19 15:41 ` [Buildroot] [PATCH 1/2] package/systemd: allow empty SYSTEMD_DEFAULT_TARGET Yann E. MORIN

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=CADYdroMqpgyCR0jyWdXR+UqiOSoNdKNN3OsGSSXDrBvR_RSyNw@mail.gmail.com \
    --to=nolange79@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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.