I was writing an ebuild for a third-party package. I needed to run autoreconf with -vfi options (as I've seen in a testing directory where I compiled it manually) I tried to write simply "eautoreconf -vfi", thinking that, as for econf and emake, those options were sent to the autoreconf. But it seems to ignore them. So I opened the eclass for eautoreconf and I've seen it doesn't call autoreconf, but it looks like re-implemented. But not those options I need for my build Reproducible: Always At the moment I have temporary fixed this problem by using autoreconf directly in my ebuild, but, of course, it should be avoided.
Unless you provide some information on which problems you got when using simple eautoreconf, this bug is not going anywhere.
(In reply to comment #1) > Unless you provide some information on which problems you got when using simple > eautoreconf, this bug is not going anywhere. > the eautoreconf ignores the "-vfi" option, needed for compiling this ebuild, because the third-party software has a sort of "chained" ./configure to be created and runned. There're many folders in the source, each of them with their configure.ac etc; to be translated into the configure script to write each Makefile. Infact, the Makefile of the main dir tries to run make for each Makefile in the subdirectories, but it isn't able to find them, of course
