From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] system: default to empty issue/hostname for custom skeleton
Date: Thu, 09 Jan 2014 21:32:15 +0100 [thread overview]
Message-ID: <87r48gaoc0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <cffd411631d99ddd729f0e29888b0fb14941889a.1389134731.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Tue, 7 Jan 2014 23:46:07 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> From: Sagaert Johan <sagaert.johan@skynet.be>
> A custom skeleton may include /etc/issue and/or /etc/hostname, in
> which case we do not want to override them.
> But those files could also be missing from the custom skeleton, or
> the user may want to override their content.
> Make the current default value for isue and hostname depend on the
> generic skeleton, and default to empty for a custom skeleton.
> Signed-off-by: Sagaert Johan <sagaert.johan@skynet.be>
> [yann.morin.1998 at free.fr: change from hiding it behind SKELETON_DEFAULT
> to use conditional default values; move below the skeleton choice;
> improve help entries]
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Do we really need to add this extra complexity? A custom skeleton is not
recommended (and in any case an advanced option), and the fix for
people not wanting /etc/issues / hostname overwritten is very easy, they
can just set it to the empty string.
What do others say?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-01-09 20:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 22:46 [Buildroot] [PATCH 0/5] Misc accumulated changes Yann E. MORIN
2014-01-07 22:46 ` [Buildroot] [PATCH 1/5] Makefile: support running graph-depends from out-of-tree Yann E. MORIN
2014-01-09 20:28 ` Peter Korsgaard
2014-01-07 22:46 ` [Buildroot] [PATCH 2/5] toolchain/external: fix wrapper by not passing conflicting flags Yann E. MORIN
2014-01-08 12:45 ` Maxime Hadjinlian
2014-01-08 15:51 ` Thomas Petazzoni
2014-01-08 15:57 ` Maxime Hadjinlian
2014-01-08 18:01 ` Yann E. MORIN
2014-01-08 18:46 ` Maxime Hadjinlian
2014-01-09 20:28 ` Peter Korsgaard
2014-01-07 22:46 ` [Buildroot] [PATCH 3/5] package/tzdata: install a default localtime Yann E. MORIN
2014-01-09 17:13 ` Arnout Vandecappelle
2014-01-09 22:57 ` Yann E. MORIN
2014-01-09 20:29 ` Peter Korsgaard
2014-01-28 21:13 ` Thomas Petazzoni
2014-01-07 22:46 ` [Buildroot] [PATCH 4/5] system: default to empty issue/hostname for custom skeleton Yann E. MORIN
2014-01-09 20:32 ` Peter Korsgaard [this message]
2014-01-09 20:44 ` Yann E. MORIN
2014-01-10 8:52 ` Sagaert Johan
2014-01-10 14:35 ` Peter Korsgaard
2014-01-07 22:46 ` [Buildroot] [PATCH 5/5] manual: add section about dealing efficiently with big image files Yann E. MORIN
2014-01-09 20:29 ` 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=87r48gaoc0.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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