Hello Mariano -

The reason I use absolute path names is to remove any ambiguity.

I suggest you try what you show below to see what you get.

regards

Hugh


On Tuesday, September 10, 2002, at 06:20 AM, Mariano Absatz wrote:

> El 6 Sep 2002 a las 9:29, Hugh Irvine escribi�:
>
>>
>> Hello Mariano, Hello Charly -
>>
>> Yes, my method allows you to use specific, different versions of Perl 
>> as
>> well.
>>
>> All I do is this:
>>
>>      cd /the/radiator/distribution
>>      /usr/local/src/Perl/Perl-..../bin/perl Makefile.PL; make; make test
> Thanx, Huhg...
>
> would
>       cd /the/radiator/distribution
>       ../bin/perl Makefile.PL; make; make test
> make the perl installation used relative path dependant? or it would 
> resolve
> the absolute path in the making?
>
> i.e:
> would I get "#!../bin/perl" at the top of my radiusd?
>
>
>>      ......
>>
>> then when I run Radiator I use the fully qualified path for both the
>> perl instance I want and for the Radiator instance I want.
>>
>>      cd /the/radiator/distribution;
>> /usr/local/src/Perl/Perl-..../bin/perl radiusd -config_file .....
>>
>> Of course I usually use constants in shell scripts to make it easier
>> (and sometimes symbolic links).
>>
>> cheers
>>
>> Hugh
>>
>>
>> On Friday, September 6, 2002, at 07:26 AM, Mariano Absatz wrote:
>>
>>> FTR,
>>>
>>> I also think it's "A Good Thing"(TM) to be able to have a special perl
>>> instalation for some critical perl programs or for programs with quite
>>> specific requirements...
>>>
>>> El 5 Sep 2002 a las 11:34, Karl Gaissmaier escribi�:
>>>
>>>> Hi Hugh and Mike,
>>>>
>>>>> Hello Charly -
>>>>>
>>>>> What I usually do is skip the "make install" step altogether, and 
>>>>> just
>>>>> leave the various versions in seperate directories.
>>>>
>>>> sounds reasonable for your environment but without a "make install"
>>>> for example the path to the perl interpreter doesn't gets adjusted
>>>> to the local requirements. Not all perl interpreters stay in
>>>> /usr/bin/perl
>>>> and there exists good reasons (at least for me) to use a totally
>>>> own perl interpreter installation to get the different needed 
>>>> packages
>>>> handled. Sure, I have also a perl interpreter under /usr/bin/perl but
>>>> this is the interpreter with the standard set of installed modules
>>>> for all workstations here.
>>>>
>>>> Anyway, I don't think this could be solved generally, but it should
>>>> be discussed in the FAQ or in the reference guide.
>>>>
>>>> Thanks for discussing and this wonderful support.
>>>>    Charly
>>>>
>
> --
> Mariano Absatz
> El Baby
> ----------------------------------------------------------
> I like cats too. Let's exchange recipes.
>
>
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>
>

--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to