diff options
| author |   Wynn Wolf Arbor <wolf@oriole.systems> | 2020-07-02 17:50:17 +0200 |
|---|---|---|
| committer |   Zac Medico <zmedico@gentoo.org> | 2020-07-02 14:37:02 -0700 |
| commit | 141ef203661248a2c29945f8c6770ce0c242eaf0 (patch) | |
| tree | 00ce690120fd09f00318fd1d847c55bd60179e47 /make.conf.example-repatch.sh | |
| parent | ecompress: optimize docompress -x precompressed comparison (diff) | |
| download | portage-141ef203661248a2c29945f8c6770ce0c242eaf0.tar.gz portage-141ef203661248a2c29945f8c6770ce0c242eaf0.tar.bz2 portage-141ef203661248a2c29945f8c6770ce0c242eaf0.zip | |
repos.conf: Use consistent list of values for boolean options
Valid values for boolean options in repos.conf are currently not managed
in a consistent manner. Some options only support 'true' and 'false',
whilst others additionally support 'yes' and 'no'. Using the latter
forms on options that do not support them will lead to unexpected
behaviour. For example, an option checking for 'true' will be disabled
when 'yes' is used. This is counter-intuitive and adds additional
burden: the user has to look up in the manual which form is accepted by
which option.
Have all boolean options consistently accept 'yes', 'no', 'true', and
'false' and make sure to document this in the portage(5) manual.
Additionally, document the default value for each.
Signed-off-by: Wynn Wolf Arbor <wolf@oriole.systems>
Signed-off-by: Zac Medico <zmedico@gentoo.org>
Diffstat (limited to 'make.conf.example-repatch.sh')
0 files changed, 0 insertions, 0 deletions