Hi,
> if you want to have all scripts run except a few, and doing that with
> variables, then you need to specify both LIVE_NOCONFIGS and
> LIVE_CONFIG_SCRIPTS in your config file, see the
> 'live-noconfig=*|noconfig=*)' case in /lib/live/config.sh.
Thanks for explaining the intended behavior. I did prefer the 3.0.12
(and earlier) behavior, but I trust you it made sense to change it for
some reason, and it's now too late to change back the behavior of
3.0.x anyway.
However, if that is the intended behavior, then I do believe there is
a documentation bug. The manpage has no mention of _SCRIPTS
(LIVE_CONFIG_SCRIPTS' name in 3.0.x), but instead it reads:
Everything but the shortcuts that can be configured with a boot
parameter can be alternatively also be configured through one or
more files.
[...]
LIVE_NOCONFIGS=SCRIPT1,SCRIPT2, ... SCRIPTn
This variable equals the 'live-noconfig=SCRIPT1,SCRIPT2, ...
SCRIPTn' parameter.
[...]
Removing existing config scripts
[...]
To avoid to always need specifing disabled scripts through
the boot parameter, a configuration file should be used, see above.
So I fail to see how one is supposed to understand, by reading this
manpage, that they can't disable specific scripts simply by using
LIVE_NOCONFIGS in a configuration file (as one could do until at least
3.0.12). Did I miss anything?
Do you prefer that I file another bug about the documentation issue,
then, or that I reopen the current one?
Cheers!
--
intrigeri, acting with his Tails hat
--
Attachment:
pgpY1WmSZnikC.pgp
Description: PGP signature