ps at phillipadsmith
Mar 21, 2012, 9:56 AM
Post #5 of 7
On 2012-03-21, at 10:50 AM, David E. Wheeler wrote:
Re: Problem with BRICOLAGE_PG_HOSTNAME and BRICOLAGE_PG_CONFIG_PATH
[In reply to]
> On Mar 21, 2012, at 9:24 AM, Phillip Smith wrote:
>> Not sure what happened there. There were some other scripts I was running that were looking for perl in /usr/local/bin/ Ö so I symlinked my perlbrew perl binary to that location. However, when I checked, it wasn't linked, but instead had a copy of the file there. Odd.
>> Anyway, I deleted that binary and re-ran the whole thing ensuring that it was running from /Users/phillipadsmith/perl5/perlbrew/perls/perl-5.14.2/bin/perl and everything worked.
>> However, one odd thing, it put some crazy password for the 'bric' user into the .conf file. Looked like a hashed password or something? Once that was replaced with the real password everything worked fine.
> If you run it in QUIET mode it defaults to a random password. Looks like itís because `ask_password()` requires that a password be input if the default is "NONE", so a random password gets around that. But if you trust all local connections (and there usually is no reason not to on a laptop), it should not matter.
> You can set a superuser password with PG_SUPERPASS. I don't see a setting for the bricolage password, probably because it ought to be different for every installation? Would be nice to automate, though. Not sure why it isnít. What happens if you set PGPASSWORD?
Well, basically how I got around all this was to:
+ make dist
+ perl Makefile.PL && make install in the dist directory, which goes through the verbose set-up
+ rm -r -f /usr/local/bricolage
+ move up to the git clone directory and perl Makefile.PL && make dev
Ö and that point, the make dev seems to have all of the information it needs, i.e., what I entered during make install for the distribution
I can't seem to get make dev to run in any mode other than quiet, which is a drag as it means I need to remember all of the arguments to pass it, e.g., apache2, no ssl, etc.
Save our in-boxes! http://emailcharter.org