New BinReloc patch

[Waldo Bastian]

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

On Mon April 19 2004 22:42, Arend van Beelen jr. wrote:
> On Monday 19 April 2004 22:34, Waldo Bastian wrote:
> [SNIP]
>
> > > 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?
>
> Because the application doesn't reliably know its own application
> directory. The only way application nowadays know it is either because of
> hardcoded paths that are set during configure or through hacks like
> environment variables. Now that has to be changed to be determined at
> runtime which is exactly what my new functions do. To ease the application
> developers the prefix of the current binary is automatically added in the
> KStandardDirs constructor, but this is exactly why these functions are
> important, to determine the application directory.

I think there is a bit of misunderstanding. I'm not against these functions, I 
I am against having these functions as part of the API. The KStandardDirs 
constructor can just call them and for that they don't need to be part of the 
API. 

Cheers,
Waldo
- -- 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
^ bastian at kde.org | Is your software SUSE LINUX READY? | bastian at suse.com
^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAhD9KN4pvrENfboIRAn0lAJ9b94bXtzvFGOfW6j08s/UzgngKzACfRNcO
N5GMvnGu/P8r+HrUnXP+oQA=
=MMuz
-----END PGP SIGNATURE-----