On Jun 12, 2021, at 13:07, Bill Cole wrote:
> On 2021-06-12 at 12:55:24 UTC-0400 (Sat, 12 Jun 2021 09:55:24 -0700)
> Ken Cunningham is rumored to have said:
>
>> macports recommended perl is still 5.28
>
> Which has been unsupported upstream for just over a year.
The point Ken was making is
On Jun 12, 2021, at 12:39, Kastus Shchuka wrote:
>> sudo port upgrade --enforce-variants git -perl5_28 +perl5_30
>
> Thank you, that worked and allowed me to uninstall all p5.28 modules.
>
> What puzzles me still, why port info shows that git depends on perl 5.28
> modules:
>
> $ port info
On Sat, Jun 12, 2021 at 06:02:25PM -0700, Ken Cunningham
wrote:
> I think Bill perhaps then you really want to open a thread with the title:
>
> “I would like to suggest we move MacPorts default perl to 5.30 now”.
>
> And then let the conversation happen, and if the outcome is “Yes” then that
I think Bill perhaps then you really want to open a thread with the title:
“I would like to suggest we move MacPorts default perl to 5.30 now”.
And then let the conversation happen, and if the outcome is “Yes” then that
will happen.
Or 5.32. Whatever you care to suggest.
But trying to fight
On 2021-06-12 at 12:55:24 UTC-0400 (Sat, 12 Jun 2021 09:55:24 -0700)
Ken Cunningham
is rumored to have said:
macports recommended perl is still 5.28
Which has been unsupported upstream for just over a year. 5.30 just fell
out of support a few weeks ago. They are doing a major release every
> On Jun 12, 2021, at 9:54 AM, Rainer Müller wrote:
>
> On 12/06/2021 18.32, Bill Cole wrote:
>> On 2021-06-12 at 12:11:47 UTC-0400 (Sat, 12 Jun 2021 09:11:47 -0700)
>> Kastus Shchuka
>> is rumored to have said:
>>
>>> I wish it could be so easy to remove perl5.28. Apparently, I have to
>>>
macports recommended perl is still 5.28
$ port info perl5
perl5 @5.28.3 (lang)
Sub-ports:perl5.16, perl5.18, perl5.20, perl5.22, perl5.24,
perl5.26, perl5.28, perl5.30, perl5.32
Variants: perl5_26, [+]perl5_28, perl5_30
so that is supposed to be the default perl for
On 12/06/2021 18.32, Bill Cole wrote:
> On 2021-06-12 at 12:11:47 UTC-0400 (Sat, 12 Jun 2021 09:11:47 -0700)
> Kastus Shchuka
> is rumored to have said:
>
>> I wish it could be so easy to remove perl5.28. Apparently, I have to
>> keep it because of git:
>
> port uninstall git
> port install git
On 2021-06-12 at 12:11:47 UTC-0400 (Sat, 12 Jun 2021 09:11:47 -0700)
Kastus Shchuka
is rumored to have said:
I wish it could be so easy to remove perl5.28. Apparently, I have to
keep it because of git:
port uninstall git
port install git -perl5_28 +perl5_30
--
Bill Cole
b...@scconsult.com
I wish it could be so easy to remove perl5.28. Apparently, I have to keep it
because of git:
$ port info git
git @2.31.1_2 (devel)
Variants: [+]credential_osxkeychain, [+]diff_highlight, [+]doc,
gitweb, [+]pcre, perl5_26, [+]perl5_28,
perl5_30, python, svn,
On 2021-06-09 at 15:51:09 UTC-0400 (Wed, 9 Jun 2021 15:51:09 -0400)
Daniel J. Luke
is rumored to have said:
On Jun 6, 2021, at 1:41 PM, Bill Cole
wrote:
I *think* I've even worked out the right way to use that construct to
make Perl upgrades simpler, so I use the p5-* ports:
I gave up on
On Jun 6, 2021, at 12:41, Bill Cole wrote:
> Not sure where the bug is here, but it's evident in 'port reclaim'.
>
> The p5-* ports are basically placeholders for the p5.##- ports. I *think*
> I've even worked out the right way to use that construct to make Perl
> upgrades simpler, so I use
On Jun 6, 2021, at 1:41 PM, Bill Cole
wrote:
> I *think* I've even worked out the right way to use that construct to make
> Perl upgrades simpler, so I use the p5-* ports:
I gave up on trying to use this in any useful way a while ago - if you've got
some way that it works, please share.
13 matches
Mail list logo
