On 2021-10-03 at 16:16:55 UTC-0400 (Mon, 4 Oct 2021 07:16:55 +1100)
Ian Wadham
is rumored to have said:
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
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.
> On 2 Oct 2021, at 6:33 pm, Ryan Schmidt wrote:
>
> On Sep 21, 2021, at 23:49, Ian Wadham wrote:
>
>> I wish to download from the Web a package called CocoaPods, however it needs
>> a developers’ package of Ruby to build it.
>>
>> I am using MacOS Catalina 10.15.7. Apple provides Ruby in
Ryan Schmidt wrote:
Ports that include the xcode portgroup also most probably require Xcode. I would have
thought that the xcode 1.0 portgroup would declare "use_xcode yes" somewhere in
it, but it doesn't seem to. Maybe that is an oversight.
It isn't. Setting build.type to "xcode" also sets
On Sat, Oct 02, 2021 at 08:56:18PM -0700, Michael wrote:
> ugh. Well, doing a search shows a LOT of articles about this very
> issue -- this was apparently a known "this is going to affect a lot of
> people" deal, and "just update your software, or ... sorry." was the
> only answer.
>
> But, I
> On 2 Oct 2021, at 6:29 pm, Ryan Schmidt wrote:
> 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
On Sat, Oct 02, 2021 at 10:32:40PM -0500, Ryan Schmidt
wrote:
> On Oct 2, 2021, at 22:06, Michael wrote:
> >
> > So, first, I want to say "Thank you" for this bit:
> >
> >> • From View menu select "Show Expired Certificates"
> >
> > In keychain access, I could not see the expired certs, and
