On Tue, 2013-03-26 at 11:37 -0400, Simo Sorce wrote: > On Tue, 2013-03-26 at 15:25 +0000, Myklebust, Trond wrote: > > On Tue, 2013-03-26 at 10:41 -0400, Simo Sorce wrote: > > > Libgssglue is not really useful anymore, it is a sort of middleman that > > > wraps the actual GSSAPI that is already pluggable/extensible via shared > > > modules. > > > > > > In particular libgssglue interferes with the workings of gss-proxy in my > > > case. > > > > > > The attached patch makes building against libgssglue optional and > > > defaults to not build against libgssglue and instead builds directly > > > against the native GSSAPI. > > > > > > ./configure --enable-gss > > > will now build against GSSAPI > > > > > > ./configure --enable-gss --with-gssglue > > > will keep building against libgssglue in case someone still needs it for > > > whatever reason. > > > > > > Simo. > > > > > > > Won't that be a backward compatibility issue? > > What are you worried about exactly ? Is there a use case we should know > about ? Building nfs-utils against existing older setups. There are a lot of users out there of 4-5 year old distros (including ones maintained by your employer). Why isn't it safe to assume that if someone has libgssglue installed, then we should be building nfs-utils against it? -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
