Adam Weinberger writes:
>> On 18 May, 2017, at 12:45, Joseph Mingrone wrote:
>> Adam Weinberger writes:
On 18 May, 2017, at 12:25, Adam Weinberger wrote:
> On 18 May, 2017, at 12:22, Luca Pizzamiglio
> wrote:
> Hi,
> node6 is the LTS, node is the current. From a sta
> On 18 May, 2017, at 12:45, Joseph Mingrone wrote:
>
> Adam Weinberger writes:
>
>>> On 18 May, 2017, at 12:25, Adam Weinberger wrote:
>
On 18 May, 2017, at 12:22, Luca Pizzamiglio
wrote:
>
Hi,
>
node6 is the LTS, node is the current. From a stability point of view,
>
Adam Weinberger writes:
>> On 18 May, 2017, at 12:25, Adam Weinberger wrote:
>>> On 18 May, 2017, at 12:22, Luca Pizzamiglio
>>> wrote:
>>> Hi,
>>> node6 is the LTS, node is the current. From a stability point of view,
>>> node6 is the choice, but node (7) is already widely used.
>>> Probab
> On 18 May, 2017, at 12:25, Adam Weinberger wrote:
>
>> On 18 May, 2017, at 12:22, Luca Pizzamiglio
>> wrote:
>>
>> Hi,
>>
>> node6 is the LTS, node is the current. From a stability point of view,
>> node6 is the choice, but node (7) is already widely used.
>> Probably, the best solution wou
> On 18 May, 2017, at 12:22, Luca Pizzamiglio
> wrote:
>
> Hi,
>
> node6 is the LTS, node is the current. From a stability point of view,
> node6 is the choice, but node (7) is already widely used.
> Probably, the best solution would be to provide the desired node
> version via Mk/bsd.default-v
Hi,
node6 is the LTS, node is the current. From a stability point of view,
node6 is the choice, but node (7) is already widely used.
Probably, the best solution would be to provide the desired node
version via Mk/bsd.default-versions.mk and then all ports depends to
the common version (like perl,
Steve Wills writes:
> Can execjs work with node6? What else would have to change to get it all
> onto node6?
It can, but other changes would be needed. For example www/gitlab pulls
in www/npm, which pulls in www/node. It also pulls in other ports that
pull in www/rubygjec-execjs.
I think the q
> On 18 May, 2017, at 11: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
Can execjs work with node6? What else would have to change to get it all
onto node6?
Steve
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
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/nod
10 matches
Mail list logo
