Most of the Config modules perform opkg_helper operations during --dry-run conditions, and rely on the opkg_helper._dry_run attribute to suppress filesystem changes. Instead, opkg will print the operation and move on.
But the _GraphicalConfig behaves differently, and instead bails out of configure() early, when in dry-run conditions.
The _Graphical Config should behave the same as the other configs, for consistency.
Related: #45
Most of the Config modules perform
opkg_helperoperations during--dry-runconditions, and rely on theopkg_helper._dry_runattribute to suppress filesystem changes. Instead, opkg will print the operation and move on.But the
_GraphicalConfigbehaves differently, and instead bails out ofconfigure()early, when in dry-run conditions.The _Graphical Config should behave the same as the other configs, for consistency.
Related: #45