buildrootschalter/package/nano/Config.in
Thomas De Schampheleire 35eaed8d07 Config.in files: use if/endif instead of 'depends on' for main symbol
In the Config.in file of package foo, it often happens that there are other
symbols besides BR2_PACKAGE_FOO. Typically, these symbols only make sense
when foo itself is enabled. There are two ways to express this: with
    depends on BR2_PACKAGE_FOO
in each extra symbol, or with
    if BR2_PACKAGE_FOO
        ...
    endif
around the entire set of extra symbols.

The if/endif approach avoids the repetition of 'depends on' statements on
multiple symbols, so this is clearly preferred. But even when there is only
one extra symbol, if/endif is a more logical choice:
- it is future-proof for when extra symbols are added
- it allows to have just one strategy instead of two (less confusion)

This patch modifies the Config.in files accordingly.

Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-12-25 12:21:39 +01:00

25 lines
515 B
Plaintext

config BR2_PACKAGE_NANO
bool "nano"
depends on BR2_USE_WCHAR
# full version uses fork()
select BR2_PACKAGE_NANO_TINY if !BR2_USE_MMU
select BR2_PACKAGE_NCURSES
help
A nice ncurses-based editor. Started out as a clone of pico.
Great editor for new users.
http://www.nano-editor.org/
if BR2_PACKAGE_NANO
config BR2_PACKAGE_NANO_TINY
bool "optimize for size"
default y
help
Disable all features for the sake of size.
endif
comment "nano needs a toolchain w/ wchar"
depends on !BR2_USE_WCHAR