On 12/27/11 13:54, Tony Whyman wrote:
> Alex,
>
> The test was simple enough. I ran the guardian under a non root account,
> using "fakeroot" to avoid the restriction on account names, and set the
> FIREBIRD environment variable to point to the Firebird directory tree
> (firebird.conf, etc.) I had created under the same account. This was a
> setup I often use with Firebird 2.1. The guardian failed reporting that
> it was under to write to
>
> /var/run/firebird/2.5/fb_guard
>
> i.e. the location where the installed software expects to save the
> fb_guard file. Directory permissions do not permit the copy of the
> guardian that I ran to write to this location. I compiled the Firebird
> sources plus Debian patch myself and confirmed the problem, I then
> compiled them with the BUILD_ROOT section commented out and the problem
> goes away for my copy. However, when run as the installed daemon, it
> fails because it now expects all Firebird files to be under
> /etc/firebird/2.5 rather than distributed about the system.
>
> If I enclose the section with
>
> if (getenv("FIREBIRD") == 0) {
>
> ...
> }
> then both my test and the installed daemon run fine.
>
> If you look at the debian/rules file you can see how the directories are
> set up for a standard debian build. The problem is that by specifying
> hard wired paths, it seems that it is no longer possible to use the
> FIREBIRD variable to specify an alternative directory tree - at least
> with the current source code.Agreed - guardian directory (and probably some others) should be overridable by environment. On the other hand, overriding all directories like you suggest is bad idea - for a debian package it's meaningless to override bin or sbin, they should always point where actual binaries are placed. Please add a ticket to the tracker. ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
