mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] rootfs: option to link /etc/resolv.conf to /lib/systemd/resolv.conf
Date: Wed, 12 Apr 2017 10:59:04 +0200	[thread overview]
Message-ID: <78d31bfe-7a73-5a1e-5e16-ec3a952490bb@gr13.net> (raw)
In-Reply-To: <20170320143435.8793-1-artur@4wiebe.de>

On 20.03.2017 15:34, Artur Wiebe wrote:
> Signed-off-by: Artur Wiebe <artur@4wiebe.de>
> ---
>  rules/rootfs.in    | 11 +++++++++++
>  rules/rootfs.make  |  3 +++
>  rules/systemd.make |  1 +
>  3 files changed, 15 insertions(+)
> 
> diff --git a/rules/rootfs.in b/rules/rootfs.in
> index 5965417e1..1b459b6d7 100644
> --- a/rules/rootfs.in
> +++ b/rules/rootfs.in
> @@ -426,6 +426,17 @@ choice
>  		  systemd-resolved and is filled with data from the systemd
>  		  managed interfaces.
>  
> +	config ROOTFS_RESOLV_STATIC

Misleading config item name.

Should clearly reflect the fact that it links to a file belonging to
one particular optional package. So, perhaps call it

   CONFIG_ROOTFS_RESOLV_SYSTEMD_STATIC

OTOH, as it's from only one of dozens optional packages that might
add/maintain local resolver config, I wonder why it's not handled
within that particular package (in that case: systemd). By the same
logic, we would also have to add similar options for all the various
dhcp clients of other network management tools within the rootfs
package. And the same for lots of other files in /etc.


--mtx


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2017-04-12  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 14:34 Artur Wiebe
2017-03-24 14:34 ` Michael Olbrich
2017-04-12  8:59 ` Enrico Weigelt, metux IT consult [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=78d31bfe-7a73-5a1e-5e16-ec3a952490bb@gr13.net \
    --to=enrico.weigelt@gr13.net \
    --cc=ptxdist@pengutronix.de \
    /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