On Tue, Mar 10, 2009 at 01:15:36PM +0100, Pierre Ossman wrote: > On Tue, 10 Mar 2009 04:11:19 -0500 > DRC <dcomman...@users.sourceforge.net> wrote: > > > The build system in TigerVNC unfortunately seems to require autoconf > > 2.61 or higher and also a later version of automake than is available on > > even the latest Enterprise Linux system (CentOS 5.2.) Thus, I cannot > > build the software, nor can anyone else running Enterprise Linux. I > > would suggest checking the configure script into the SVN repository. > > The RealVNC source code does this. It will give advanced users the > > option to chance the autoconf files as they see fit but will not require > > the use of autoconf/automake for the more mundane builds of the software. > > > > Checking in generated files is always a slippery slope, so I'm against > this.
Well, I don't think so. Many projects have autogenerated files (like configure, Makefile.in, config.h.in etc) in their VCS due reason which Darell wrote above. It is common practice, AFAIK. When you update your autoconf and friends, you simply regenerate all stuff. > But I don't see why we need a newer autoconf than what CentOS ships. > Does anyone know? That's the issue that should be fixed IMO. I will check it tomorrow. But I think the best solution will be check-in autogenerated files if at least one of our developers uses "older" system. (Debian Etch, CentOS 5.x etc) Regards, Adam -- Adam Tkac, Red Hat, Inc. ------------------------------------------------------------------------------ _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
