On 2023/09/19 13:13, Aaron Bieber wrote: > On 9/19/23 13:10, Stuart Henderson wrote: > > On 2023/09/19 21: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.
Doesn't seem all that old? 2022 and only one version behind the latest on https://github.com/yarnpkg/yarn/releases/ > > > 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? > > > > > security/vault/Makefile: > > > > : # UI prebuilt with: cd ui; yarn install; npm rebuild node-sass; yarn run > > build > > : DISTNAME= vault-vendored-${VERSION} > > : PKGNAME= vault-${VERSION} > > : > > : ### Vault UI > > : MODGO_FLAGS= -tags=ui > > : MASTER_SITES= https://distfiles.tristero.se/ > > > > Wonder if it would make sense to add devel/yarn as a build dep for cases > like this? > I don't think so - it's not used during build, only to prepare updates (and that would restrict the archs on whih vault can be built; node's ONLY_FOR_ARCHS is shorter than vault's).
