Created attachment 220724 [details]
Update to 1.22.10
The patch take into consideration the new slave port yarn-node14 (bug #251966).
I doubt this only affects you. In fact it affects all admins who use yarn and would like to stay with the next LTS release of node, node14. The npm port was updated ages ago with the NODE14 knob. Is the yarn port dead?
It would be really nice to see this (or a similar) patch commited before python27 and node12 are deleted from the ports.
Thanks for submitting, I'll commit it in the next days.
(In reply to Markus Mann from comment #1)
yarn port is not dead, sometimes I'm busy and it takes time to get what I want to do in the port tree, but you can always fill a PR.
yarn 1 is not super active anymore, because of yarn2, that is not distributed as independent package any longer
A commit references this bug:
Date: Wed Dec 30 17:20:13 UTC 2020
New revision: 559675
www/yarn-*: update to 1.22.10
Add support for Node 14
Fix CONFLICTS with an updated list of nodejs versions
Submitted by: Jose Luis Duran <email@example.com>
The original patch didn't work, plist checks were failing.
Moreover, I created the yarn-node14 port and fix all the CONFLICTS declaration in all other slave ports (yarn-port10 and yarn-port12)
(In reply to Luca Pizzamiglio from comment #4)
Created attachment 221109 [details]
Had to chmod +x the bins
It's weird that I had to chmod +x the bins. I'll wait for the pkg to be ready.
Thank you again!