New BinReloc patch

[Leo Savernik]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Montag 19 April 2004 22:34 schrieb Waldo Bastian:
[...]
> > Now the exact use of these functions is to locate data files that might
> > be installed with the binary, but not in a standard location. This
> > location can then be used as an *additional* location to find its files,
> > but such a location is not guaranteed to be found.
>
> KStandardDirs locates data files and when the application-directory has
> been added as prefix it will look relative to the application-directory as
> well. Why is that not enough?

This is especially useful for stand alone applications that build upon KDE 
technology, but don't strive to integrate too tightly with KDE. They could 
then store stuff in directories like

/opt/my-app/share/my-junk
/opt/my-app/share/more-specific-stuff

How would the app get to those directories with KStandardDirs?
Usually such an application will use a compiled in prefix to resolve those 
paths.

They certainly could link to binreloc again, but why making them duplicate 
efforts if it's already contained in kdelibs?

(Though I agree that such a function should be #ifdef LINUX)

>
[...]

mfg
	Leo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQFAhEFZj5jssenUYTsRAkoWAJ47CufqJtnGSxkpZ67GDydVw7+hHgCfWa7V
cqzB/biJMggPQ3Gt/PQExQE=
=Lu8H
-----END PGP SIGNATURE-----