The sample config files in the Asterisk distribution and packages are really good for getting the demo up and running quickly, for example, to extend the demo to run behind a WebRTC proxy only required about 6 lines of extra code to define a peer in sip.conf and enable TCP
However, I’m not sure that they should be installed by default by packages.
Most package managers provide a way to diff the files and merge new config options that appear in a new release
However, because a lot of things have to be ripped out of the default config to harden it and disable the demo, a simple diff doesn’t really help somebody upgrading to a new version, because usually they’ve altered the files quite dramatically
I’d suggest that the config for the demo could be placed under
/usr/share/asterisk/samples while the configs installed to /etc/asterisk should be fairly minimal
My own workaround at the moment involves tracking the released configs in a git repository and tracking my changes on a branch. However, working with the package manager diff output would help a lot more people and make it much more like other packages they are familiar with.