On Fri, 2013-01-25 at 04:41:55 +0100, Matthias Klose wrote: > Am 24.01.2013 23:40, schrieb Guillem Jover: > > Indeed, that's what I thought too when I first read Matthias report, > > using LD_LIBRARY_PATH is really not a good idea given the interactions > > with the interpreter and any forked process, I'm fixing this now to be > > included for 1.17.x to either use a different environment variable, or > > better yet to add the new option, and probably start issuing warnings > > when the variable is set. > > Note that LD_LIBRARY_PATH is usually already set by fakeroot, so a warning > might not be appropriate.
Oh right, I was already considering some heuristic to avoid bogus warnings, as in only warn if the new method is used and LD_LIBRARY_PATH is defined or something like that, but given that all/most builds will be using fakeroot, that would always trigger. Also removing support for LD_LIBRARY_PATH could break old builds in strange and difficult to diagnose ways, so there's no much point in nagging about it. Instead this should probably be handled by a lintian check so that people (not using debhelper) switch. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
