On Mon, Nov 15, 2010 at 5:39 PM, Niels Mayer wrote: > I noticed that bristol-0.40.7-7 updated due to the following security > update. What got me curious is what kind of security issue could > running bristol possibly pose?? -- none on it's own, but another rogue > package could exploit this issue ... for whatever its worth, ardour had the same issue. there's a more elegant fix than the one shown in that bug report though. the general form is:   LD_LIBRARY_PATH=StuffToAddToLdLibraryPath${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}