From owner-freebsd-ports@freebsd.org Tue May 16 10:22:51 2017 Return-Path: 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 87513D6EDD3 for ; Tue, 16 May 2017 10:22:51 +0000 (UTC) (envelope-from bradleythughes@fastmail.fm) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B2D919C3 for ; Tue, 16 May 2017 10:22:50 +0000 (UTC) (envelope-from bradleythughes@fastmail.fm) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id B4ACC205AF; Tue, 16 May 2017 06:22:49 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Tue, 16 May 2017 06:22:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=37G+d+fQ/pKriH29/d oh11WbbPDoElNAPKdecBscIrs=; b=vnwNCMiuvFgbf3sn6hnhX/uewvLPXvaKg2 h76+tD+J595vZftOsUQa8oYa/gL/UIJylW3kfTCd1UD9aP/Kf7THaFTrIk3BIDvY R9/O3ZZP6ldRLHINU3Y/1Db27FK7g0f681cTa2e0rIBbCyA9daZgpUA/KI3himxp qcunhB/lUy/JTleyKQ1McWVRWRXG6sTRhh+9xc4/DsoJoIaXyZ437NHmPaATXRKT KSsFjYZBJ+yRddnpD0gKgEVcO12KKWpW2FaejPLMVrrFbSt0PkUPYPxWzybnNxwX T2C6XXtjg2PY7qiw63U4guedeny6jutRMYxg+ytYvW/mhS1tMKJA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=37G+d+fQ/pKriH29/doh11WbbPDoElNAPKdecBscIrs=; b=dEFyZ6mx Uh4IQHVScFGmNmw1kMlcm48OjXgpTLoJp+7IVrWz1bJNv+QXkKk1cf2Lq820Ahsx gIY/SYI/rZ0O2q5wEb5SG/qCmkSC1wO9v0uTJYS8hhn2+wt41BQ/0K1g+xM1RGOO PMOpuk5q84XMaBEA8P5p8xohdFZLZED+EsX1NEP3Sk/bg1yKFz4LR6/tYDa0s7yD 7YjXgOOgo9/QKLGTr8F2tCOdCWDANc65wbMvgXMC+mG/ZmBLXtbYft0XUrgB6To7 Zj5ogLx2OmQBFvZad3F0VjuyjJr0xpRVH53T5UaBN/7vrmwaB4HJ7MLbVzCMjTk4 fRpjiIWXerPhhA== X-ME-Sender: X-Sasl-enc: DEebsDYt/630cq8kEnhKtuaE963rKemj1jRfILi//nAn 1494930169 Received: from [192.168.0.74] (ip84-247-189-242.breiband.no [84.247.189.242]) by mail.messagingengine.com (Postfix) with ESMTPA id 1B13A7E2B0; Tue, 16 May 2017 06:22:48 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: How should we name node-js ports ? From: "Bradley T. Hughes" In-Reply-To: <5254fffe-b0e1-5912-c868-9057369da9ef@bebik.net> Date: Tue, 16 May 2017 12:22:47 +0200 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <155F7AD7-95F8-447A-A052-C29396B53245@fastmail.fm> References: <32cbf11f-5ce0-ce16-8c56-c45d585ed2f6@FreeBSD.org> <53BBD762-9A8B-4582-B65D-27D752B567BF@adamw.org> <5254fffe-b0e1-5912-c868-9057369da9ef@bebik.net> To: Rodrigo Osorio X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2017 10:22:51 -0000 > On 15 May 2017, at 20:22, Rodrigo Osorio wrote: >=20 >=20 > Hi Adam, >=20 > Thanks for your feedback. >=20 > On 05/15/17 18:52, Adam Weinberger wrote: >>> On 15 May, 2017, at 6:57, Ruslan Makhmatkhanov = wrote: >>>=20 >>>=20 >>> npm packages can be installed by yarn as well; nodejs is really the = common name and makes a better prefix. >>>=20 >>> 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. I agree with this sentiment. It also does not sit well with me to use = one package manager (pkg) to run another package manager (npm) to = install dependencies. In my expereince, Node.js apps tend to have their dependencies installed = locally, as it is too easy to get into conflicts or incompatibilities = with globally installed versions. The exception to the rule is for = things that install a runnable command, like grunt-cli, npm, mocha, and = so on. >>> 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. Like expressed above, I think the "remains available to other and can be = reused as dependencies for others" can be more harmful than helpful. -- Bradley T. Hughes bradleythughes@fastmail.fm