Skip to content

Resolve #361 by zapping existing chroots after init

clayton craft requested to merge fix/361_zap_after_init into master

This extends zap() to add a 'no_confirm' option (False by default), and zap() is now called by init with no_confirm=True to automatically zap any existing chroots after the user runs init. This helps insure that what is installed in the chroots is exactly what the user expects after setting options in init.

Merge request reports