From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] boot/systemd-boot: new package
Date: Sat, 15 Dec 2018 14:47:11 +0100 [thread overview]
Message-ID: <20181215134711.GH2625@scaer> (raw)
In-Reply-To: <CADvTj4o3UQOnhq3ewP_tLGxE4bwnMP-At3zU6PLJEUmqZhM7Uw@mail.gmail.com>
James, All,
On 2018-12-15 04:09 -0700, James Hilliard spake thusly:
> On Sat, Dec 15, 2018 at 4:00 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2018-12-15 03:43 -0700, James Hilliard spake thusly:
> > > systemd-boot needed to be built at the same time as the userspace
> > > tools for systems that have a systemd init system for the integration
> > > to work properly.
> > OK, so we need to think it a bit, then. Is it the boot part that needs
> > the userland part, of the userland that needs the boot part, of they
> > both need to know each other?
> Mostly userland that needs to know the boot part, the boot part itself
> doesn't really care what OS it is booting.
OK, so we should be able to build systemd-boot as its own package.
Then, we just configure systemd with boot support.
> > One option I can think of quickly, is that we could have a systemd-boot
> > package that is only available when systemd is not enabled, and an option
> > in systemd to install the boot part when systemd is enabled.
> I was trying to avoid having fully separate packages since that would
> create a lot of maintenance overhead keeping both up to date as well.
> Is there something wrong with having a fake boot package that
> configures the appropriate options in the primary systemd package?
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.
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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2018-12-15 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 11:42 [Buildroot] [PATCH v2 1/1] boot/systemd-boot: new package james.hilliard1 at gmail.com
2018-12-15 8:58 ` Yann E. MORIN
2018-12-15 9:12 ` James Hilliard
2018-12-15 10:27 ` Yann E. MORIN
2018-12-15 10:43 ` Peter Korsgaard
2018-12-15 10:47 ` James Hilliard
2018-12-15 10:49 ` Yann E. MORIN
2018-12-15 10:43 ` James Hilliard
2018-12-15 11:00 ` Yann E. MORIN
2018-12-15 11:09 ` James Hilliard
2018-12-15 13:47 ` Yann E. MORIN [this message]
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=20181215134711.GH2625@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.