![](https://seccdn.libravatar.org/avatar/5b748275c3dbb1ceee18ed554486547d.jpg?s=120&d=mm&r=g)
On Thursday 2015-11-26 12:04, Petr Tesarik wrote:
However, these legacy distributions contain ancient versions of GNU autotools and friends, so autoreconf does not work properly when building for those targets (missing features, bugs). The scripts included in the upstream tarball are definitely better. Is it OK if I do _not_ run autoreconf in the specfile?
It is not only OK, but even preferred not to run autoreconf, as long as there is no problem with the included configure script.
I see. I probably shouldn't have accepted submitrequest 325452 back then (sorry Jan!). I'm going to remove the autoreconf stuff completely (including the libtool BuildRequires that prevents building on SLE10).
Hm? 325452 is impertinent to the question; 325452 does one thing: to create configure if it did not exist yet -- without a configure script present, %configure would not ever run. And if a configure script is already present, the check does no harm. In other words, 325452 is justified to stay, I think. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org