ruby-select problem - Sonoma

[Chris F]

Thanks Bill, Chris - I have created an appropriate .bash_profile (as 
described in the Guide) and everything appears normal now.

I've searched back to the time when Migration Assistant restored my user 
directory. That .bash_profile had several comments made at the time(s) 
that MacPorts install post-flight added and export of an amended PATH, 
but I couldn't find a comment that corresponded to my most  recent 
Macports install (which was shortly after finishing with Migration 
Assistant). However, that absence could have been due to the timing of 
backups. In any case, the restored .bash_profile should have worked just 
fine, so I'm at a loss to know how my  .bash_profile became "corrupted" 
post restoration.

Never mind - all good now. Thanks again.

Chris F


>
>> On 20 Oct 2023, at 6:13 pm, Bill Cole<macportsusers-20171215 at billmail.scconsult.com>  wrote:
>>
>> On 2023-10-19 at 18:47:01 UTC-0400 (Fri, 20 Oct 2023 11:47:01 +1300)
>> Chris F<chris at unwired.co.nz>
>> is rumored to have said:
>>
>>>> On 20/10/23 11:17 am, Chris Jones wrote:
>>>>
>>>>
>>>>> On 19 Oct 2023, at 10:58 pm, Chris F<chris at unwired.co.nz>  wrote:
>>>>>
>>>>> 
>>>>>
>>>>> I've just migrated to Sonoma 14.0 via a clean OS install plus Migration Assistant and I'm now reinstalling my ports one at a time.
>>>>>
>>>>> Port ruby31 installed without problems but ruby-select doesn't seem to work/be effective - after ruby-select ruby31 runs successfully, command "ruby" still starts the OS default ruby 2.6.10
>>>>>
>>>>> I've checked /opt/local/bin/ruby and it points (correctly?) to ruby3.1.
>>>>>
>>>>> Any advice would be appreciated.
>>>>>
>>>> Did you start a new terminal session after run port select for ruby ?
>>> Yes I did, Chris - I shut terminal down and restarted it a couple of times as well.  Chris F
>> Check the order of directories in your $PATH environment variable. If the sub-directories under /usr are listed before those under /opt/local, you will use the base install executables instead oF those installed by MacPorts.
> Exactly. If once you have started a fresh terminal
>
>   > which ruby
>
> Doesn’t list the macports provided one, the issue is your personal PATH is not set correctly.
>
> Chris
>
>>
>>
>> --
>> Bill Cole
>> bill at scconsult.com  orbillcole at apache.org
>> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
>> Not Currently Available For Hire

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20231021/7bea5f7b/attachment.htm>