On 03/27/2016 09:59 PM, Adriano dos Santos Fernandes wrote: > Em 27/03/2016 15:38, Michal Kubecek escreveu: >> On Sun, Mar 27, 2016 at 10:36:34AM -0300, Adriano dos Santos Fernandes wrote: >>> So, if we want these files for people build sources more easily, we >>> should include them in git. >> Putting generated files into git would mean developers would have to >> take care not to include them in their commits - and from time to time >> someone will forget. It might be also annoying if e.g. "git diff" shows >> you those two lines you actually changed and few hundred lines changed >> in configure just because you have different version of autoconf. >> >> I guess I could live with that as I'm not really a fan of building in >> the git working directory but many developers do that as it can make >> things easier and faster (e.g. when bisecting). >> > If configure is stored, I guess I don't need to normally run autogen.sh > so it will not be changed, will it?
As long as you do not modify configure.ac - you need not. But the problem is that if someone with relatively old autoconf did run autogen.sh old (and in the worst not ideal) configure will get into the tree. I.e. we need to validate it in some way before releasing version. I think that we do not need that additional problems and therefore should not change existing dumb method to generate tarball as long as we do not have same quality with new one. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
