Please no, I'm working on electron and I need it. VSCode works for me on amd64 (also stretchly, byar, signal-desktop). I don't know a lot about Yarn port itself but we can improve it for sure.
I think that's too early to bring my wip on ports@ but it's a start. If some brave souls want to help, I can share, just contact me. On 26/03/2024 20:10, Volker Schlecht wrote: > Picking up on that discussion from September: > > devel/yarn is > > - unsupported upstream > - unmaintained > - unused > - outdated > > ok to remove? > > On 2023-09-19 21:43, Volker Schlecht wrote: >> On Tue Sep 19, 2023 at 9:05 PM CEST, Aaron Bieber wrote: >>> On 9/19/23 13:00, Volker Schlecht wrote: >>> > Cc: abieber@ >>> > >>> > I just came across our port of devel/yarn, which appears to be both very >>> > old and by now, very underutilized. >>> > >>> > The last discussions about yarn that I saw on the list were about WIP >>> > efforts to port VSCode, to which an ancient devel/yarn doesn't seem to >>> > be the key either. >>> > >>> > Any reason to still keep it around? >>> >>> Probably not. The MainReason™ for the port was to give people a working >>> yarn. Out of the box >>> it doesn't know the path to `node`. >> >> With no regard to my: Is that still a problem since we fixed that with a >> metaphoric hammer? >> >> https://github.com/openbsd/ports/blob/master/lang/node/patches/patch-src_env_cc >
