All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Suggestion for config menu help for path values
Date: Tue, 22 Jun 2010 21:10:57 +0000 (UTC)	[thread overview]
Message-ID: <hvr8t1$io0$1@dough.gmane.org> (raw)

Just a suggestion for anytime somebody is working on the config menu
help for an option that allows a path to be entered: always specify in
the item's help whether an absolute path is required, and if not,
where the starting point is for a relative path.

For several different options, it's taken me many guesses to figure
out from what working direction a relative path should be referenced.
When each guess requires a build from-scratch, you can spend hours
trying to figure out what path value to enter for a particular script
or config file.

Right now I'm trying to figure out the CWD when the post-build script
is called, and I'll submit a help patch when I figure out the answer.

Another source of confusion I've run into a few times are cases where
the title for a config item doesn't match up with either the config
variable name or the phrase commonly used elsewhere to refer to that
item.  For example, it takes a bit if digging to figure out that in
the config menus, what the documentation calls the "post-build
script", who's value is "BR2_ROOTFS_POST_BUILD_SCRIPT" is titled
"Custom script to run before packing files".

A title including the words "post build script" would seem to be a
more obvious/consistent choice.

-- 
Grant Edwards               grant.b.edwards        Yow! !  I'm in a very
                                  at               clever and adorable INSANE
                              gmail.com            ASYLUM!!

             reply	other threads:[~2010-06-22 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 21:10 Grant Edwards [this message]
2010-06-22 21:31 ` [Buildroot] Suggestion for config menu help for path values Grant Edwards
2010-06-23  7:04 ` Thomas Petazzoni
2010-06-23 13:53   ` Grant Edwards

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='hvr8t1$io0$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.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 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.