From owner-freebsd-ports@freebsd.org  Mon May 15 18:28:42 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DB6DD6EA04
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 15 May 2017 18:28:42 +0000 (UTC) (envelope-from ros@bebik.net)
Received: from smtp.osorio.me (smtp.osorio.me [5.196.94.126])
 by mx1.freebsd.org (Postfix) with ESMTP id 4AB296E6
 for <freebsd-ports@freebsd.org>; Mon, 15 May 2017 18:28:41 +0000 (UTC)
 (envelope-from ros@bebik.net)
Received: from [192.168.1.117] (unknown [78.194.61.125])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by smtp.osorio.me (Postfix) with ESMTPSA id 8B3351978E
 for <freebsd-ports@freebsd.org>; Mon, 15 May 2017 18:22:43 +0000 (UTC)
Subject: Re: How should we name node-js ports ?
To: freebsd-ports@freebsd.org
References: <ba4cd1f6-2bd7-f710-2e6c-56c470c5ef7d@bebik.net>
 <32cbf11f-5ce0-ce16-8c56-c45d585ed2f6@FreeBSD.org>
 <53BBD762-9A8B-4582-B65D-27D752B567BF@adamw.org>
From: Rodrigo Osorio <ros@bebik.net>
Message-ID: <5254fffe-b0e1-5912-c868-9057369da9ef@bebik.net>
Date: Mon, 15 May 2017 20:22:43 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <53BBD762-9A8B-4582-B65D-27D752B567BF@adamw.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 May 2017 18:28:42 -0000


Hi Adam,

Thanks for your feedback.

On 05/15/17 18:52, Adam Weinberger wrote:
>> On 15 May, 2017, at 6:57, Ruslan Makhmatkhanov <rm@FreeBSD.org> wrote:
>>
>>
>> npm packages can be installed by yarn as well; nodejs is really the common name and makes a better prefix.
>>
>> That said, making node ports does not sit well with me. npm/yarn manages node packages. Things will break if a user has those same packages installed globally and tries to update or remove them, or if a user needs specific global versions installed.
>>
>> Rodrigo, I think your better option is simply to bundle those dependencies yourself, at the specific versions that your port requires, and install them to a private location.
I decide to split the dependencies in several packages and I use npm a 
short perform the package installation before
the staging. That way node packages remains available to other and can 
be reused as dependencies for others node ports.

>
> # Adam
>
>