Comment 1 for bug 1817121

This sounds like a good idea.

I think it may already be possible to turn this on on a package by package basis, using the options parameter to queue_install in lib/charms/apt.py. I haven't tried it, and don't even know the correct sytax. Making it easier to do this on a package by package basis would be a good feature.

Turning it on globally also seems like a good feature, and requires less thought on design. It would be easy enough to create a layer option to allow the default to be changed. It will create another point of contention between principal and subordinate charms, if they have differing config. There is no real solution when this conflict occurs, so I think package by package would be a better option, as it makes setting conflicts less likely to occur, as well as letting the charm specify which packages it is modifying config, and which packages it is using unmodified.

If we add a global option, is is debatable if it should be enabled by default. I don't think there is a correct answer, so we will need to go with the less wrong answer.