From: | David Wheeler <david(at)kineticode(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Suggestion: Which Binary? |
Date: | 2006-04-01 01:09:36 |
Message-ID: | E974F21E-FC85-4DAF-B6B3-E94040FC094D@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mar 31, 2006, at 15:52, Tom Lane wrote:
> The more usual way to handle this sort of thing is to put each version
> of perl in a different directory, and then you can alter PATH while
> running configure to pick which one you want. I've got several
> versions
> of perl on this machine that I select that way ... it doesn't require
> any special smarts on the part of the perl-using program, and it
> scales
> to handle multiple versions of other things like Tcl, too.
I would normally do that, as well, but in this case, I wanted my self-
compiled Perl to always be what runs (as a general rule), so I had it
hard link itself in /usr/bin as well as /usr/local/bin. It is only in
this one case where I need the stock Perl to be found that things get
wonky for me. :-)
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | David Wheeler | 2006-04-01 01:11:04 | Re: Suggestion: Which Binary? |
Previous Message | Tom Lane | 2006-04-01 00:01:18 | Re: Suggestion: Which Binary? |
From | Date | Subject | |
---|---|---|---|
Next Message | David Wheeler | 2006-04-01 01:11:04 | Re: Suggestion: Which Binary? |
Previous Message | Tom Lane | 2006-04-01 00:01:18 | Re: Suggestion: Which Binary? |