On Saturday 17 September 2011 14:34:20 Thiago Macieira wrote: > On Saturday, 17 de September de 2011 10:07:20 Sune Vuorela wrote: > > On 2011-09-17, Thiago Macieira <[email protected]> wrote: > > > Tell me this: how would you write code that searches for a generic > > > libexec (no "kde4" in the pathname) and yet allows KDE to find its > > > helper tools?
That's my question to this list :-) Actually, thinking about it, I have one idea: appending /libexec to every entry in LD_LIBRARY_PATH. Would that work? > > And even write one generic enough to work across distributions. > > > > Debian and friends uses more or less /usr/lib/NAME/libexec > > where as fedora and friends uses /usr/libexec/NAME/ What's NAME there? The package name, in order to split up the helper binaries from different packages? Do we really need this? After all /usr/bin has no such split. > The big difference there is whether those executables are > architecture-specific in multiarch configurations (e.g., > /usr/lib64/NAME/libexec). Usually they aren't. How could an executable not be architecture-specific? I must be missing something. -- David Faure, [email protected], http://www.davidfaure.fr Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org). _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
