Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] wpa_supplicant: install basic configuration file
Date: Wed, 25 Apr 2012 00:03:30 +0200	[thread overview]
Message-ID: <20120425000330.638f4e37@skate> (raw)
In-Reply-To: <87pqawga6d.fsf@macbook.be.48ers.dk>

Hello,

Le Tue, 24 Apr 2012 22:13:46 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

>  yegorslists> +define WPA_SUPPLICANT_INSTALL_CONFIG
>  yegorslists> +	$(INSTALL) -m 644 \
>  yegorslists> +	  package/wpa_supplicant/wpa_supplicant.conf  $(TARGET_DIR)/etc/wpa_supplicant.conf
> 
> Normally we only install these default files if not already present in
> the rootfs, so people can put their own version in the skeleton if they
> need something else. See ifplugd for an example.

I am less and less sure this is a scenario we should support. We have
been talking for a while of removing the ability of using a custom
target skeleton, and instead recommend all users to use the post-build
script capability, which is much more appropriate.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-04-24 22:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  6:55 [Buildroot] [PATCH v2 1/2] wpa_supplicant: install basic configuration file yegorslists at googlemail.com
2012-04-23  6:55 ` [Buildroot] [PATCH v2 2/2] dbus: bump to 1.4.20 yegorslists at googlemail.com
2012-04-24 20:09   ` Peter Korsgaard
2012-04-24 20:13 ` [Buildroot] [PATCH v2 1/2] wpa_supplicant: install basic configuration file Peter Korsgaard
2012-04-24 22:03   ` Thomas Petazzoni [this message]
2012-04-25  6:23   ` Yegor Yefremov
2012-05-09 20:37 ` 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=20120425000330.638f4e37@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox