All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/3] package/iwd: add basic configuration file
Date: Sun, 14 Jun 2020 23:48:27 +0200	[thread overview]
Message-ID: <20200614234827.2208bc3a@gmx.net> (raw)
In-Reply-To: <20200614213610.GQ2346@scaer>

Hello Yann,

On Sun, 14 Jun 2020 23:36:10 +0200, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Peter, All,
>
> On 2020-06-14 23:28 +0200, Peter Seiderer spake thusly:
> > On Sun, 14 Jun 2020 22:57:15 +0200, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > > On 2020-06-14 21:07 +0200, Peter Seiderer spake thusly:
> > > > On Sun, 14 Jun 2020 11:56:29 +0200, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > > > > > +	select BR2_PACKAGE_OPENRESOLV if !BR2_INIT_SYSTEMD
> [--SNIP--]
> > > I'm still not convinced...
> > > What if one has:
> > >     BR2_INIT_SYSTEMD=y
> > >     # BR2_PACKAGE_SYSTEMD_RESOLVED is not set
> > > Does systemd still provides resolv.conf?
> > > I guess not. So in fact the dependency is really not about the init
> > > system. but about a package that provides resolv.conf. In which case it
> > > should be changed to:
> > >     select BR2_PACKAGE_OPENRESOLV if !BR2_PACKAGE_SYSTEMD_RESOLVED
> > Or:

> > 	select BR2_PACKAGE_OPENRESOLV if !BR2_INIT_SYSTEMD

This one fixes it for all non-systemd init systems...

> > 	select BR2_PACKAGE_SYSTEMD_RESOLVED if BR2_PACKAGE_SYSTEMD

This one fixes it for systemd-init-system implemented with BR2_PACKAGE_SYSTEMD...

>
> No sorry, that still does not make sense to me... :-(
>
>
> For one, the conditions are not homogeneous: in one case you test
> against the init system, in the other you test against the package.
>
> [--SNIP--]
> > And what is about the LIBFOO_INSTALL_INIT_OPENRC mentioned in [1]?
>
> Aha! If not specified, it defaults to using the sysv hook, quoting:
>
>     The only exception is when openrc is chosen as init system and
>     LIBFOO_INSTALL_INIT_OPENRC has not been set, in such situation
>     LIBFOO_INSTALL_INIT_SYSV will be called, since openrc supports
>     sysv init scripts.

So, what do with the openrc-init case (for the config file)?

Regards,
Peter

>
> Regards,
> Yann E. MORIN.
>

  reply	other threads:[~2020-06-14 21:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 23:24 [Buildroot] [PATCH v1 1/3] package/iwd: needs dbus (runtime) Peter Seiderer
2020-06-12 23:24 ` [Buildroot] [PATCH v1 2/3] package/iwd: add basic configuration file Peter Seiderer
2020-06-14  9:56   ` Yann E. MORIN
2020-06-14 19:07     ` Peter Seiderer
2020-06-14 20:57       ` Yann E. MORIN
2020-06-14 21:28         ` Peter Seiderer
2020-06-14 21:36           ` Yann E. MORIN
2020-06-14 21:48             ` Peter Seiderer [this message]
2020-06-15  7:22               ` Yann E. MORIN
2020-06-15 18:09                 ` Peter Seiderer
2020-06-15 20:02                   ` Yann E. MORIN
2020-06-15 18:41         ` Peter Seiderer
2020-06-15 20:03           ` Yann E. MORIN
2020-06-12 23:24 ` [Buildroot] [PATCH v1 3/3] package/iwd: add sysv init script Peter Seiderer
2020-06-14 10:00   ` Yann E. MORIN
2020-06-14 19:22     ` Peter Seiderer
2020-06-14  9:44 ` [Buildroot] [PATCH v1 1/3] package/iwd: needs dbus (runtime) Yann E. MORIN
2020-07-13  6:39 ` Peter Korsgaard

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=20200614234827.2208bc3a@gmx.net \
    --to=ps.report@gmx.net \
    --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.