Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1 v2] Hide issue and hostname menu when using a custom skeleton.
Date: Sun, 5 Jan 2014 18:41:15 +0100	[thread overview]
Message-ID: <20140105174115.GE16066@free.fr> (raw)
In-Reply-To: <1358102400-9628-1-git-send-email-sagaert.johan@skynet.be>

Sagaert, All,

On 2013-01-13 19:39 +0100, Sagaert Johan spake thusly:
> Only show hostname and issue options when the default skeleton is selected.
> Moved the menu sections so that when a custom skeleton is selected the 
> issue and hostname options are hidden.

After fiddling with the idea, I believe we should not do it that way.

It can well happen that a custom skeleton does not already have an
hostname or issue file, and we may want to create either or both in this
case.

So I think we should do it differently:

    config BR2_TARGET_GENERIC_HOSTNAME
        string "System hostname"
        default "buildroot" if BR2_ROOTFS_SKELETON_DEFAULT
        default ""          if ! BR2_ROOTFS_SKELETON_DEFAULT
        help
          Select system hostname to be stored in /etc/hostname.
          Leave empty to not create /etc/hostname, or to keep the
          one from a custom skeleton.

And system/system.mk already ensures we do not create /etc/hostname if
BR2_TARGET_GENERIC_HOSTNAME is empty.

That way, the default is correct in both cases, and it is still possible
to create/override hostname and issue for a custom skeleton.

(Ditto for /etc/issue).

Thoughts?

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.  |
'------------------------------^-------^------------------^--------------------'

      parent reply	other threads:[~2014-01-05 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-13 18:39 [Buildroot] [PATCH 1/1 v2] Hide issue and hostname menu when using a custom skeleton Sagaert Johan
2013-08-13 22:11 ` Thomas Petazzoni
2013-08-13 22:29   ` Yann E. MORIN
2013-08-14 12:37   ` Gustavo Zacarias
2014-01-05 17:41 ` 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=20140105174115.GE16066@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox