jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-29 06:06:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs/manual: size of tab in package description

Browse Source 
Explicitly state that one tab counts for 8 columns in package
description, leaving 62 characters to the text itself.
Update the text and the example in the two places where the Config.in
format is described.
Also mention a newline is expected between the help text itself and the
upstream URL.

This blob can help developers to understand the expected formatting.
Also, it can be referenced by reviewers.

http://patchwork.ozlabs.org/patch/611289/
http://patchwork.ozlabs.org/patch/606866/
http://patchwork.ozlabs.org/patch/459960/

Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Romain Naour <romain.naour@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Ricardo Martincoski 2017-02-19 19:17:22 -03:00 committed by Thomas Petazzoni
parent 8e87d76c12
commit ad35a3a43d
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/manual/adding-packages-directory.txt
View File

@ -28,7 +28,8 @@ contain:
config BR2_PACKAGE_LIBFOO config BR2_PACKAGE_LIBFOO
bool "libfoo" bool "libfoo"
help help
This is a comment that explains what libfoo is. This is a comment that explains what libfoo is. The help text
should be wrapped.
http://foosoftware.org/libfoo/ http://foosoftware.org/libfoo/
--------------------------- ---------------------------
@ -36,8 +37,9 @@ config BR2_PACKAGE_LIBFOO
The +bool+ line, +help+ line and other metadata information about the The +bool+ line, +help+ line and other metadata information about the
configuration option must be indented with one tab. The help text configuration option must be indented with one tab. The help text
itself should be indented with one tab and two spaces, lines should itself should be indented with one tab and two spaces, lines should
not be longer than 72 columns, and it must mention the upstream URL be wrapped to fit 72 columns, where tab counts for 8, so 62 characters
of the project. in the text itself. The help text must mention the upstream URL of the
project after an empty line.
As a convention specific to Buildroot, the ordering of the attributes As a convention specific to Buildroot, the ordering of the attributes
is as follows: is as follows:

6
docs/manual/writing-rules.txt
View File

@ -29,7 +29,8 @@ config BR2_PACKAGE_LIBFOO
depends on BR2_PACKAGE_LIBBAZ depends on BR2_PACKAGE_LIBBAZ
select BR2_PACKAGE_LIBBAR select BR2_PACKAGE_LIBBAR
help help
This is a comment that explains what libfoo is. This is a comment that explains what libfoo is. The help text
should be wrapped.
http://foosoftware.org/libfoo/ http://foosoftware.org/libfoo/
--------------------- ---------------------
@ -40,7 +41,8 @@ config BR2_PACKAGE_LIBFOO
* The help text itself should be indented with one tab and two * The help text itself should be indented with one tab and two
spaces. spaces.
* The help text should be wrapped to fit 72 columns. * The help text should be wrapped to fit 72 columns, where tab counts
for 8, so 62 characters in the text itself.
The +Config.in+ files are the input for the configuration tool The +Config.in+ files are the input for the configuration tool
used in Buildroot, which is the regular _Kconfig_. For further used in Buildroot, which is the regular _Kconfig_. For further