-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/03/10 18:26, Peter Stuge wrote: > David Sommerseth wrote: >> it's a requirement to be able to build OpenVPN on RHEL4.6. > > As Alon explained, building is not the problem. autotools are used > when preparing git source for build. This is done for every release, > so that there is a ready-made configure script included in the > tarball. > > When building a release (or snapshot, if there are any) from such a > tarball then autoconf is no longer relevant, it was run only when the > tarball was created. > > RHEL4.6 can easily build a release that was prepared using the most > recent autoconf. That RHEL4.6 system doesn't need autoconf installed > at all. > > The only way autoconf on that RHEL4.6 would be relevant is if those > RHEL4.6 systems strictly need to build directly from git source, as > opposed to building from a prepared tarball. Is that the case?
I will get that clarified on the meeting tomorrow, as this might be a scenario. But to be honest, I have troubles seeing that people want to do active development on RHEL4.6, at least do changes which require changing autotools files or pulling down SVN or git trees. kind regards, David Sommerseth -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkuX2PUACgkQDC186MBRfrpN2QCgn5/NRRY9Je63J6Lgx1LJVjWg WC0AoIDf6ZCBo3ulh3K1JakEnL8u+zXa =adty -----END PGP SIGNATURE-----
