On Tue, 27 Oct 2009 02:13:03 +0100, Henrik Nordstrom <[email protected]> wrote: > tis 2009-10-20 klockan 12:52 +1300 skrev Amos Jeffries: > >> We can do that yes. I think I would also rather do it too. It paves the >> way for a clean deprecation cycle now that TPROXYv4 kernels are >> effectively >> mainstream: >> >> 3.0: (2008-2010) TPROXYv2 with libcap + libcap2 >> 3.1: (2010-2012) support TPROXYv2 + TPROXYv4 with libcap2 >> 3.2: (2011?) support TPROXYv4 with libcap2 > > So you want me to add the patch back on trunk? > > Means we must update libcap on several of the build farm members, > including the master, or disable TPROXY in the build tests.. > > I guess I could add some configure magics to look for the missing > function and automatically disable..
Yes please. I would like the patch to be updated with said function test logic to auto-disable libcap2, modulo a fatal death on the --with-* case. Then for it to go back in :) Amos
