On Thu, Nov 08, 2012 at 10:49:20PM -0000, Adam Stokes wrote:
> I think a corner case may arise if a amd64 system requests use of that
> library but only the i386 version is installed, but, I think the risk of
> that happening is slim to none.
Yep, that's an understood corner case at any rate, and the intended behavior
is still to set the variable if the proxy module is installed for *any*
architecture. If the variable is set and you run a program for an
architecture that we don't have the menuproxy for, you get warnings on
stderr. If the variable isn't set and you run a program for an architecture
that we *do* have the menuproxy for, you get reduced functionality.
On Thu, Nov 08, 2012 at 10:49:20PM -0000, Adam Stokes wrote:
> I think a corner case may arise if a amd64 system requests use of that
> library but only the i386 version is installed, but, I think the risk of
> that happening is slim to none.
Yep, that's an understood corner case at any rate, and the intended behavior
is still to set the variable if the proxy module is installed for *any*
architecture. If the variable is set and you run a program for an
architecture that we don't have the menuproxy for, you get warnings on
stderr. If the variable isn't set and you run a program for an architecture
that we *do* have the menuproxy for, you get reduced functionality.