MacPorts to install Python. So I had a look
>> at python_select’s portfile and discovered the existence of the “port
>> select” command. Even then it is not easy to find. There are about a dozen
>> occurrences of the word “select” in the “man port” output and I was
>> won
actually exists or if it is just some internal
> function of portfiles and MacPorts scripts.
>
> All of the above occupied several frustrating days of my time.
>
> So this is why I say the portfile for ruby_select is broken. Several
> “ruby$NN” packages depend on it.
>
> M
lly exists or if it is just some internal function of portfiles
and MacPorts scripts.
All of the above occupied several frustrating days of my time.
So this is why I say the portfile for ruby_select is broken. Several “ruby$NN”
packages depend on it.
MacPorts’ Python gives a new user something
n/ruby2.6
>>> Also, the port actually called “ruby” is very old (version 1.8.7) and “port
>>> notes ruby” deprecates it. Should it be removed from MacPorts?
>>
>> If nobody needs it, I suppose it could be removed. Do you know that nobody
>> needs it? I don't know t
Policy: openmaintainer
I think this is because the port file named “ruby_select”, on
which each Ruby port depends, is broken.
But it is not broken.
The ruby_select port is what provides the information that 'port select'
needs to make links to a specific set of Ruby binaries.
Hi Christopher,
In brief, MacPorts’ “port select” command is working fine at the command-line
in Catalina… but the problem is with installing ANY version of ruby, not
switching between multiple versions of ruby that are already installed.
In a machine where no MacPorts Ruby is installed, the
> The ruby_select portile just has:
>
> destroot {
> select::install ruby ${filespath}/base
> select::install ruby ${filespath}/none
> }
>
> which does not redirect the commands “ruby” or “gem” to the appropriate
> version when you have installed the port “ruby27” for example.
now that.
>
>> Or reincarnated as “ruby18”, dropping “ruby186” as well?
>
> If it ain't broke, don't fix it?
Port “ruby_select” is broken.
Port “ruby” wasted my time because it looked as though it would be the default
one to install, but then at the end of installation it deprecated itself.
Cheers,
Ian Wadham.
On Sep 25, 2021, at 23:14, Ian Wadham wrote:
> MacPorts contains packages of many versions of Ruby, similarly to the Python
> and Perl groups, but the corresponding “ruby_select” port does not
> automatically create the links needed to access commands “ruby”, “gem” etc. I
> was able to get
I use rvm to install Rubies. But some folks like rbenv.
Sent from my iPad
> On Sep 25, 2021, at 9:14 PM, Ian Wadham wrote:
>
> Hi guys,
>
> MacPorts contains packages of many versions of Ruby, similarly to the Python
> and Perl groups, but the corresponding “ruby_select” port does not
>
Hi guys,
MacPorts contains packages of many versions of Ruby, similarly to the Python
and Perl groups, but the corresponding “ruby_select” port does not
automatically create the links needed to access commands “ruby”, “gem” etc. I
was able to get around this by using “sudo port select”
11 matches
Mail list logo
