situation with www/node6 and www/node

Steve Wills steve at
Thu May 18 17:30:14 UTC 2017

Can execjs work with node6? What else would have to change to get it all
onto node6?


On 05/18/2017 13:22, Joseph Mingrone wrote:
> Hello,
> I am hitting an issue where the conflicting www/node6 and www/node
> packages are attempting to be installed together.  For example, the
> upcoming net-im/mastodon pulls in www/yarn (which depends on www/node6
> by default), and indirectly depends on devel/rubygem-execjs (which
> depends on www/node by default).
> It would be ideal if all ports depended on the same node version by
> default.  Looking at the current state of the ports tree, it would make
> sense for everything to depend on www/node since the only two ports
> depending on www/node6 by default are www/npm3 and www/yarn.  But, Luca
> makes the point that version 7 of node is not what upstream recommends.
> Could we come to a consensus here?
> Thanks,
> Joseph

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 638 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the freebsd-ports mailing list