From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael S. Zick Date: Sun, 13 Nov 2011 06:45:01 -0600 Subject: [Buildroot] [PATCH 2/5] doc: mention how to format the Config.in file In-Reply-To: References: Message-ID: <201111130645.03086.minimod@morethan.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Sun November 13 2011, Thomas Petazzoni wrote: > Signed-off-by: Thomas Petazzoni > --- > docs/manual/adding-packages-directory.txt | 5 +++++ > 1 files changed, 5 insertions(+), 0 deletions(-) > > diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt > index a262a8c..b61eb54 100644 > --- a/docs/manual/adding-packages-directory.txt > +++ b/docs/manual/adding-packages-directory.txt > @@ -24,6 +24,11 @@ config BR2_PACKAGE_LIBFOO > http://foosoftware.org/libfoo/ > --------------------------- > > +The +bool+ line, +help+ line and other meta-informations about the > +configuration option must be indented with one tab. The help text > +itself but be indented with one tab and two spaces, and it must s/but/should/ Mike > +mention the upstream URL of the project. > + > Of course, you can add other sub-options into a +if > BR2_PACKAGE_LIBFOO...endif+ statement to configure particular things > in your software. You can look at examples in other packages. The