Dave Page wrote:
Thanks for the link. We do already have a plist file - the only sensible
option I can think of is to add /usr/local/pgsql/bin (and whereever the
dports version installs if it's different) to the path in it and hope
the user installs PostgreSQL there. We can always include a note
John DeSoi wrote:
I think that I can find a way to copy pg_dump and pg_restore into the
bundle (during "make install"), but I'll be very busy the
next few days,
so it'll have to wait until the weekend.
OK, great - thanks.
Excellent, I think this is the best option.
The latest nighty build,
Dave Page wrote:
On 14/12/05 9:12 pm, "Dave Page" wrote:
On 14/12/05 7:05 pm, "Jerry LeVan" <[EMAIL PROTECTED]> wrote:
I guess the subject says it all. I replaced 1.4.0 with
1.4.1 and many, many commands kill the application.
(even select * from foo limit 100).
Eeep, that's not good :-(. I'm
Dave Page wrote:
Does anyone have an Intel Mac that they would be willing do try building
pgAdmin on? There's certainly one script that will fail, but I'm kinda
hoping that will be all :-). It would be good to know for sure, and be
able to fix the script (lines 20/26 of
http://svn.pgadmin.org/cgi
Dave Page wrote:
The OSX build was an automate build run by Florian - I don't know what
happened to that. I can probably run it on a box in my office if
Florian's is permanently offline.
The harddrive in the old G3 crashed and burned (probably literally
speaking, judging from the sounds it pro
