Michael Biebl wrote: >2007/12/16, Alexander Neundorf <[EMAIL PROTECTED]>: >> Hi, >> >> attached you can find a small patch which changes the default value of >> the option KDE4_USE_ALWAYS_FULL_RPATH from OFF to ON. >> A better name for that option would be "KDE_BUILD_LIBS_WITH_RPATH", >> then I wouldn't have to explain what it does. >> >> Pros: libs should always have the correct RPATH >> Cons: "make install" will take longer, since libs then also have to be >> relinked (as long as cmake without chrpath support is used) > >Hi Alex, > >do you know about >http://people.debian.org/~che/personal/rpath-considered-harmful >or >http://wiki.debian.org/RpathIssue > >Considering the issues raised there, what's your answer to this?
The document explains rather well why RPATH is not allowed in Debian. Which is why we provide packagers the ability to turn RUNPATH (not RPATH, since we're disabling that in KDE) off. Indeed, I do recommend doing that if the target path is or will be in the dynamic linker's search paths. But the document does not consider the case where the user does not have system administration privileges. If he cannot modify /etc/ld.so.conf and cannot install libraries to /usr/lib or somewhere where ld.so.conf points to, then he'd end up with a KDE that doesn't run. Therefore, RUNPATH is not only a good thing, it's a *necessity*. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
