On Feb 11, 2010, at 7:07 PM, Andrew Dunstan wrote:
>
>
> Alexey Klyukin wrote:
>> On Feb 11, 2010, at 6:24 PM, Andrew Dunstan wrote:
>>
>>
>>> Alexey Klyukin wrote:
>>>
Hello,
When developing pl/perlu functions common definitions and methods are
often stored in exte
Alexey Klyukin wrote:
On Feb 11, 2010, at 6:24 PM, Andrew Dunstan wrote:
Alexey Klyukin wrote:
Hello,
When developing pl/perlu functions common definitions and methods are often
stored in external .pm modules. During deployment the modules should be
installed somewhere in @INC to
On Feb 11, 2010, at 6:24 PM, Andrew Dunstan wrote:
>
>
> Alexey Klyukin wrote:
>> Hello,
>>
>> When developing pl/perlu functions common definitions and methods are often
>> stored in external .pm modules. During deployment the modules should be
>> installed somewhere in @INC to be reachable
Alexey Klyukin wrote:
Hello,
When developing pl/perlu functions common definitions and methods are often
stored in external .pm modules. During deployment the modules should be
installed somewhere in @INC to be reachable by the perl interpreter. However,
installing the modules to a location
Hello,
When developing pl/perlu functions common definitions and methods are often
stored in external .pm modules. During deployment the modules should be
installed somewhere in @INC to be reachable by the perl interpreter. However,
installing the modules to a location outside of the PG install
