> > > sbuild.conf changes occasionally upstream with new watches > > > and alternatives and I'll be tracking that. The user > > > shouldn't have to pay much attention to the file. > > > > And marking it as conffile allows that. If the user didn't change the > > file, it will be replaced with the new version. If he did, he'll need > > to merge by hand. > > > > If I want to shoot myself in the foot, please allow me to do so. > > I'd rather not have either a conffile. Currently the user has to > 'N' on installing a new sbuild.local.conf but it's a nobrainer - > no diff or thinking required as everything in the new file is > commented out. > Only if the file was changed. And if it was changed, I expect to be notified when a new version would replace it. If it is left as it is, it will be automatically updated to the new version, without human interaction. > I was trying to get away from user interaction during install. I > was going to go with the following but didn't get around to it, > > - leave /etc/sbuild.conf a configuration file. This will be for > upstream changes only. > If you don't mark it as a conffile, be sure to preserve changes anyway, or you're violating Policy (11.7.3).
Attachment:
pgpZKF_nR_MSu.pgp
Description: PGP signature