From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5 v5] boot/systemd-boot: new package
Date: Fri, 11 Jan 2019 06:59:17 +0100 [thread overview]
Message-ID: <20190111055917.GC2428@scaer> (raw)
In-Reply-To: <6c1edf5d-e6b3-9453-96a3-4f7aa9480a44@mind.be>
Arnout, All,
On 2019-01-11 00:47 +0100, Arnout Vandecappelle spake thusly:
> On 26/12/2018 09:52, Yann E. MORIN wrote:
> > Since systemd-boot is really part of systemd, when systemd is enabled
> > (as an init system), we rely on it to build the boot blobs, and
> > systemd-boot (this package) is not available.
> >
> > Now, when systemd is not enabled, systemd-boot (this package) will
> > actually build the boot blobs, and only that. No userspace tool is
> > built.
> I really don't like this approach of copying systemd.
>
> I would instead try harder to keep the standalone version part of the systemd
> package itself. Yes, I realize that I'm coming very late with this... The only
> reason we got here is this statement from Yann:
>
> >> What is wrong is that it makes the systemd package *and* the init
> >> selectionmuch more copmplex, and this is not acceptable (IMHO).
> >>
> >> I'd rather have a second package that is trivial, with mimimum, if at
> >> all, changes in the main systemd package.
>
> The second package turns out not to be trivial at all...
Yes, because it *is* non trivial as upstreeam does not make it trivial.
But once it is posible to (basically) do in systemd:
cd $(@D)/src/boot; meson
ninja -C $(@D)/src/boot build
ninja -C $(@D)/src/boot install
Then I still think it is better to just create a new package for
systemd-boot standalone, rather than piggy-back on systemd.
Afterall, we already had this discussion back with mesa3d-headers, when
I initially tried to piggy-back on mesa3d, but was told to make a
separate package. And we have linux-headers that is separate from linux,
or uboot-tools that is separate from uboot...
[--SNIP--]
> Finally note that I fully agree that we should not even start support for
> standalone systemd-boot until upstream progresses into making it buildable
> standalone. I really don't want that huge patch either. But that's independent
> of how standalone systemd-boot is implemented.
It's almost orthogonal, yes. But my point is, it's not because it is the
same source tree that it should be the same package in Buildroot.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-01-11 5:59 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 8:52 [Buildroot] [PATCH 0/5 v5] systemd-boot: new simple EFI bootloader replacing gummmiboot (branch yem/systemd-boot) Yann E. MORIN
2018-12-26 8:52 ` [Buildroot] [PATCH 1/5 v5] package/meson: never try to run generated target binaries Yann E. MORIN
2018-12-28 10:54 ` Thomas Petazzoni
2018-12-26 8:52 ` [Buildroot] [PATCH 2/5 v5] package/meson: fix CPU familly Yann E. MORIN
2018-12-28 10:54 ` Thomas Petazzoni
2018-12-26 8:52 ` [Buildroot] [PATCH 3/5 v5] core/pkg-infra: allow meson packages to specify custom build rules Yann E. MORIN
2018-12-26 11:36 ` James Hilliard
2018-12-26 12:06 ` Yann E. MORIN
2018-12-27 4:21 ` James Hilliard
2018-12-27 8:23 ` Yann E. MORIN
2018-12-28 10:54 ` Thomas Petazzoni
2018-12-26 8:52 ` [Buildroot] [PATCH 4/5 v5] package/systemd: enable building of systemd-boot Yann E. MORIN
2018-12-26 8:52 ` [Buildroot] [PATCH 5/5 v5] boot/systemd-boot: new package Yann E. MORIN
2018-12-26 9:33 ` Yann E. MORIN
2018-12-26 21:23 ` Thomas Petazzoni
2018-12-26 21:37 ` James Hilliard
2018-12-26 21:43 ` Thomas Petazzoni
2018-12-26 21:52 ` James Hilliard
2018-12-26 21:41 ` Yann E. MORIN
2018-12-26 22:07 ` James Hilliard
2018-12-26 22:12 ` James Hilliard
2018-12-26 22:52 ` James Hilliard
2018-12-27 1:27 ` James Hilliard
2018-12-27 8:49 ` Yann E. MORIN
2018-12-27 9:07 ` James Hilliard
2018-12-27 9:11 ` Yann E. MORIN
2018-12-27 9:13 ` James Hilliard
2018-12-27 10:40 ` Yann E. MORIN
2018-12-27 10:42 ` James Hilliard
2018-12-27 10:57 ` Yann E. MORIN
2018-12-27 11:01 ` James Hilliard
2018-12-29 9:35 ` Yann E. MORIN
2018-12-29 10:50 ` James Hilliard
2018-12-29 11:38 ` Yann E. MORIN
2018-12-29 11:43 ` James Hilliard
2018-12-30 8:44 ` James Hilliard
2018-12-31 10:16 ` Yann E. MORIN
2018-12-31 10:24 ` James Hilliard
2018-12-31 10:36 ` Yann E. MORIN
2018-12-31 12:43 ` Peter Korsgaard
2019-01-10 23:47 ` Arnout Vandecappelle
2019-01-11 5:59 ` Yann E. MORIN [this message]
2019-01-11 6:47 ` James Hilliard
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=20190111055917.GC2428@scaer \
--to=yann.morin.1998@free.fr \
--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 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.