I think we shouldn't sponsor this.
If corsac bumped the debhelper revision to 7.0.50, there might be a reason and that's actually the case: See the debian/rules: #!/usr/bin/make -f
LDFLAGS+=-Wl,-z,defs -Wl,--as-needed
override_dh_auto_configure: dh_auto_configure -- --prefix=/usr --enable-animation
binary: dh binary --before dh_shlibdeps rm -f debian/gtk2-engines-murrine/usr/lib/gtk-2.0/2.10.0/engines/libmurrine.la dh_gtkmodules dh binary --remaining
%: dh $@
-> the override management in debhelper is only accessible in debhelper 7.0.50 (http://kitenet.net/~joey/blog/entry/debhelper_dh_overrides/), so typically, --prefix=/usr --enable-animation will be ignored.
I think we shouldn't sponsor this.
If corsac bumped the debhelper revision to 7.0.50, there might be a reason and that's actually the case:
See the debian/rules:
#!/usr/bin/make -f
LDFLAGS+ =-Wl,-z, defs -Wl,--as-needed
override_ dh_auto_ configure:
dh_auto_configure -- --prefix=/usr --enable-animation
binary: gtk2-engines- murrine/ usr/lib/ gtk-2.0/ 2.10.0/ engines/ libmurrine. la
dh binary --before dh_shlibdeps
rm -f debian/
dh_gtkmodules
dh binary --remaining
%:
dh $@
-> the override management in debhelper is only accessible in debhelper 7.0.50 (http:// kitenet. net/~joey/ blog/entry/ debhelper_ dh_overrides/), so typically, --prefix=/usr --enable-animation will be ignored.