>>>>> "Thomas" == Thomas Goirand <z...@debian.org> writes:
Thomas> Now, I have another example, which is quite the opposite one
Thomas> of what you gave as example:
Thomas>
https://salsa.debian.org/openstack-team/debian/openstack-debian-images/blob/debian/stein/debian/rules
Thomas> Why would one want to switch that one to something else? The
Thomas> package, basically, consists of a shell script and a man
Thomas> page only. The minimalism of this package doesn't require an
Thomas> over-engineered dh sequencer, does it? I'm happy the way the
Thomas> package is, and I don't think I'd switch to the dh sequencer
Thomas> *UNLESS* someone has a better argument than "it's new", or
Thomas> "debian/rules will be smaller", or even "it's going to
Thomas> evolve without you even noticing it" (which is more scary
Thomas> than anything else, which is IMO one of the defects of the
Thomas> dh sequencer).
Could you make an attempt at articulating this as an exception?
That is, openstack-debian-images should not use dh because <something
generic that could be evaluated against other packages>
