>>>>> "Bernd" == Bernd Paysan <[email protected]> writes:
> Am Sonntag, 2. Dezember 2012, 17:46:03 schrieb David Kuehling: >> Hi, >> >> I just found out that a Gforth installed in /usr/ does not by default >> search for include files from /usr/local/share/gforth/site-forth. >> And on the other hand, a Gforth in /usr/local does not search for >> /usr/share/gforth/site-forth. >> >> This is different from how the site-emacs directory is handled in >> Emacs. It also makes it very difficult to package a forth program or >> library that correctly installs on 'make install'. >> >> This forces me to install my forth library in a application-specific >> directory outside site-forth, adding a corresponding 'also-path' >> command in my scripts. >> >> Where there any reasons for restricting the forth path in this way? > Well, we just use @datadir@ from autoconf to know where the data has > been installed in. Your suggestion would be to add > /usr/share/site-forth/@package@ to the path if @datadir@ is > /usr/local/share, and to add /usr/local/share/site-forth/@package@ if > it is /usr/share? Yes, something like that. Just like default PATH usually allows execution of programs from both /usr/local/bin and /usr/bin, or default GCC include search path allows use of files from both /usr/include and /usr/local/include. cheers, David -- GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk.gpg Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40
pgp6ZuV8VWSJy.pgp
Description: PGP signature
