Hi there, On 19.02.2017 22:40, Rolf Leggewie wrote: > On 19.02.2017 19:45, David Rabel wrote: >> I think you are wrong here. intltoolize is not run by autoreconf. > > That's what I read during my research about dh-autoreconf (not > autoreconf). It's entirely possible that I am mistaken. As I said, my > changes were untested. Does the package still compile?
No, it doesn't. > By the way, why do you remove the autogenerated files in the first place > when upstream apparently is keen to ship them and it creates a "problem" > for you in having to recreate them? Actually because I thought I wouldn't have to include them into debian/copyright and I wasn't sure about some of the licenses. ;) Of course that was not the only reason. I thought it would make everything more clean. So we could just leave them in place? > This is usually only necessary if > those autogenerated files are old and do not support newer platforms. > That's when you need to autoreconf. Otherwise, it's unnecessary but it > does have the benefit of future-proofing the package somewhat. I cannot remember, why I added --with autoreconf . I did so half a year ago and I wasn't smart enough to make notes or to use version control from the beginning. I _think_ it was because Makefile.in.in was a symlink back then and I wanted to override it during the build process, because lintian reported an error about this. I will try to build the package without --with autoreconf later. Yours David
signature.asc
Description: OpenPGP digital signature
